!> Caution! Unexpected difficulties with the Translator App move2_loc to MovingPandas might lead to errors in new Workflows that contain Python Apps. Some of the Python Apps currently give errors, the developers of these Apps are working on new versions to get these Apps working again. Meanwhile, please continue using your old Workflows when using these Apps (with the deprecated Movebank Location move1 starting App). Please bear with us, we will inform you when the updates are completed. (22 Nov 2024)
The Apps on MoveApps are based on different programming languages (currently R and Python), and each App uses functions that require a specific input type and provide a specific output type. Thus, each App is characterised by those two input/output (IO) types.
In the general overview of all the Apps (the App Browser) these IO types are specified in the rightmost column "Input/Output".
Before you start a Workflow, it is advisable to use the App Browser to find the Apps that you would like to use for your analysis. Some IO types can be translated into each other and Apps of those types can therefore be used in the same Workflow. For connecting Apps of different IO types, use the Translator Apps.
When adding a new App to the Workflow by clicking on the + only those Apps that match the IO type(s) of the adjacent App(s) will appear in the list (see How to Create a Workflow for instructions on how to build a Workflow).
Note the message above the list of Apps: In our example, it is informing that only Apps that have an input and output type move2::move2_loc are listed.
There are a series of Apps in the category Translator within the class Helper to enable the usage of the wide spectrum of available Apps. These Apps translate data types so Apps that have different IO types can be used in one Workflow. After adding a Translator App to the Workflow, Apps with another IO type can be added.
In the "Input/Output" column of a Translator App you can quickly see what output/input types are being translated.
!> Be aware that not all input/output types can be translated into all other types. These have to be equivalent. E.g. ctmm::telemetry.list cannot be translated into a move2::move2_nonloc as the first contains location data (e.g. GPS) and the second contains non-location data (e.g. acceleration).