Aws panorama code#

'interface': 'accountXYZ::people_counter.people_counter_container_binary_interface ', 'name': 'people_counter_container_binary_node ', 'interface': 'accountXYZ::call_node.callable_squeezenet_interface ' 'name': 'panorama::abstract_rtsp_media_source ', In that case, interface was linked to the model asset which we added using that command.ДЄt this point, graph.json under the graphs directory looks like this Similarly, a new interface was added to the call-node package when we can add-raw-model command.

Aws panorama code#

If output of your code needs to be consumed by another asset, that can be part of the ouputs. In this example, the code just expects one input which is a video stream. In this case, since our asset is a container with your code in it, all the inputs your code expects can be part of the inputs under interfaces. That means that we are defining an interface to that asset. For example, people_counter_container_binary_interface has an asset field which points to people_counter_container_binary. In Panorama, interfaces are a way to programtically interact with a package and each interface is linked to an asset. 'asset': 'people_counter_container_binary ',ДЄ new asset named people_counter_container_binary has been added under assets and a new interface named people_counter_container_binary_interface has been defined. 'name': 'people_counter_container_binary_interface ', 'name': 'people_counter_container_binary ', 'description': 'Default description for package people_counter ', People_counter package has the core logic to count the number of people, so let's create a file called people_counter_main.py at packages/accountXYZ-people_counter-1.0/src and add the relevant code to that.Д®dit packages/accountXYZ-people_counter-1.0/descriptor.json to have the following content If you make any updates to your model or desriptor.json file after running this command, just re-run the command with the same -model-asset-name and the old asset will be updated with the new assets. Successfully downloaded compiled artifacts (s3:// /squeezenet1_0.tar.gz) to. $ panorama-cli add-raw-model -model-asset-name callable_squeezenet -model-s3-uri s3:// /raw_models/squeezenet1_0.tar.gz -descriptor-path packages/accountXYZ-call_node-1.0/descriptor.json -packages-path packages/accountXYZ-call_node-1.0Дownload: s3:// /squeezenet1_0.tar.gz to assets/callable_ Since call_node has the model in this example, edit packages/accountXYZ-call-node-1.0/descriptor.json and add the following snippet into it. Values used in this example are specific to the squeezenet model that is being used in this example. All models for this reason are paired with a descriptor.json which has the required meta deta for compiling the raw model on the cloud.Дetails about using Sagemaker Neo to compile models can be found at ДЄll the model info that is used to compile models on Sagemaker Neo are part of the descriptor.json. Raw models are compiled using Sagemaker Neo on Panorama Cloud before being deployed onto the device. More details about connecting this camera are discussed in the app graph section below Preparing a model for Panorama Rtsp_v1_interface is the defined interface for an abstract camera and it has an output port called video_out which can be used to forward the camera output to another node. 'description': 'Default description for camera front_door_camera ' 'interface': 'panorama::abstract_rtsp_media_source.rtsp_v1_interface ', Developer is not expected to make any changes in this directory. More about container package management later.ДЄssets directory is where all the assets reside. In people_counter package which is the default i.e container type, all the implementation related files go into the src directory and descriptor.json has details about which command and file to use when the container is launched. Model package call-node has a descriptor.json which needs to have the metadata required for compiling the model. Interface definitions for the package need to be defined in this as well. Package.json in each package has details about the package and the assets it uses. Nodes and Edges are the way to define an application graph in Panorama. Graph.json under graphs directory lists down all the packages, nodes and edges in this application. $ panorama-cli create-package -name call_node -type Model Application StructureДЄt this point, the application structure looks as follows. $ panorama-cli create-package -name people_counter

Successfully created the project skeleton at $ panorama-cli init-project -name example_project