rights reserved. Presenter: Haichen Shen, Yao Wang Amazon SageMaker Neo, Deep Engine Science Dynamic Model in TVM AWS AI© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Models with models© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Support dynamic model in TVM ● Support Any-dim in typing ● Use shape function to compute the type at runtime ● Virtual input_name = "data" input_shape = [tvm.relay.Any(), 3, 224, 224] dtype = "float32" block = get_model('resnet50_v1', pretrained=True) mod, params = relay.frontend.from_mxnet(block, shape={input_name:

Memory Model C++11 – C++23About Me: alex.dathskovsky@speedata.io www.linkedin.com/in/alexdathskovsky https://www.cppnext.comAlex Dathskovsky | alex.dathskovsky@speedata.io | www.linkedin.com/in/a

application and integrate it into the CMS. Create a plugin model In the models.py of polls_cms_integration add the following: This creates a plugin model class; these all inherit from the cms.models.pluginmodel pluginmodel.CMSPlugin (or a sub- class thereof) and not models.Model [https://docs.djangoproject.com/en/4.2/ref/models/instances/#django.db.models.Model]. Create and run migrations: The Plugin Class Now create plugin naming is: PollPluginModel: the model class PollPluginPublisher: the plugin class A second convention is also countered quite frequently: Poll: the model class PollPlugin: the plugin class You don’t

application and integrate it into the CMS. Create a plugin model In the models.py of polls_cms_integration add the following: This creates a plugin model class; these all inherit from the cms.models.pluginmodel pluginmodel.CMSPlugin (or a sub- class thereof) and not models.Model [https://docs.djangoproject.com/en/4.2/ref/models/instances/#django.db.models.Model]. Create and run migrations: The Plugin Class Now create plugin naming is: PollPluginModel: the model class PollPluginPublisher: the plugin class A second convention is also countered quite frequently: Poll: the model class PollPlugin: the plugin class You don’t

take a basic Django opinion poll application and integrate it into the CMS. 4.1. Create a plugin model In the models.py of polls_cms_integration add the following: from django.db import models from cms on_delete=models.CASCADE) def __str__(self): return self.poll.question This creates a plugin model class; these all inherit from the cms.models.pluginmodel.CMSPlugin base class. Note django CMS plugins pluginmodel.CMSPlugin (or a sub- class thereof) and not models.Model [https://docs.djangoproject.com/en/2.2/ref/models/instances/#django.db.models.Model]. Create and run migrations: python manage.py makemigrations

take a basic Django opinion poll application and integrate it into the CMS. 4.1. Create a plugin model In the models.py of polls_cms_integration add the following: from django.db import models from cms on_delete=models.CASCADE) def __str__(self): return self.poll.question This creates a plugin model class; these all inherit from the cms.models.pluginmodel.CMSPlugin base class. Note django CMS plugins pluginmodel.CMSPlugin (or a sub- class thereof) and not models.Model [https://docs.djangoproject.com/en/2.2/ref/models/instances/#django.db.models.Model]. Create and run migrations: python manage.py makemigrations

going to take a basic Django opinion poll application and integrate it into the CMS. Create a plugin model In the models.py of polls_cms_integration add the following: from django.db import models from cms ForeignKey(Poll, on_delete=models.CASCADE) def __str__(self): return self.poll.question This creates a plugin model class; these all inherit from the cms.models.pluginmodel.CMSPlugin base class. Note: django CMS plugins plugins inherit from cms.models.pluginmodel.CMSPlugin (or a sub-class thereof) and not models.Model. 4.1. Django/Python compatibility table 17 django cms Documentation, Release 3.10.0 Create and run migrations:

going to take a basic Django opinion poll application and integrate it into the CMS. Create a plugin model In the models.py of polls_cms_integration add the following: from django.db import models from cms ForeignKey(Poll, on_delete=models.CASCADE) def __str__(self): return self.poll.question This creates a plugin model class; these all inherit from the cms.models.pluginmodel.CMSPlugin base class. Note: django CMS plugins plugins inherit from cms.models.pluginmodel.CMSPlugin (or a sub-class thereof) and not models.Model. Create and run migrations: python manage.py makemigrations polls_cms_integration python manage.py migrate

__init__.py admin.py models.py tests.py views.py my_site/ static/ project.db requirements.txt The Plugin Model In your poll application’s models.py add the following: from django.db import models from cms.models Note: django CMS plugins inherit from cms.models.CMSPlugin (or a subclass thereof) and not models.Model. 5.1. Tutorials 13 django cms Documentation, Release 3.0.19.dev1 The Plugin Class Now create a file from django.utils.translation import ugettext as _ class CMSPollPlugin(CMSPluginBase): model = PollPlugin # model where plugin data are saved module = _("Polls") name = _("Poll Plugin") # name of the plugin