The dashboard is a graphical web interface that allows user to create, edit, execute and inspect the outputs of an analysis Run. To access your dashboard, open a web browser and navigate to https://www.dapta.com. Then log in with your user credentials and click on the ‘Dashboard’ button that has appeared in the main website menu.
New : Reset the workspace. Also use this to delete your session from the Cloud after completing a Run.
Open : Open a saved workspace session by uploading a JSON-formatted session definition file.
Download : Download a JSON-formatted version of your current session and the Run Log (if available).
View Log : View the current Run Log (if available).
… : View menu of secondary controls, useful links and new features.
Right-click in the workspace to open a workspace context menu. Select the ‘Add Empty Node’ option to add an empty template Component to the session.
Scroll to zoom-in or out.
Select the workspace controls + and - to zoom in and out, or the ◻ to fit all Components into the current view.
? : Pending : Some inputs are missing.
🗸 : Valid : All necessary inputs have been defined.
! : Invalid : Some inputs are erroneous.
Design variable connection : transfer design variable values (numbers or arrays of numbers only) between Components. They appear as black arrows in the workspace view. Updated variables are transferred after every origin Component calculation iteration. This is the default Connection type.
Implicit variable or file connection : transfer implicit variables (any JSON serialisable object) or files between Components. They appear as green arrows in the workspace view. Updated variables are transferred after every origin Component calculation iteration. This is the default Connection type for file Connections.
Setup variable or file connection : transfer setup variables (any JSON serialisable object) or files between Components. They appear as blue arrows in the workspace view. Updated variables are transferred only once after all Components completed setup and before the first compute of the connection target Component.
The data transferred through Connections has to be a JSON serialisable python object (this includes most python data types) or a file reference. File reference keys start with the prefix “files.” .
The compute functions will always be executed in order from a single ‘Start Node’ to a single ‘End Node’. This means that a ‘Start Node’ may not have any incoming connections, and an ‘End Node’ may not have any outgoing connections. Driver components cannot have any connections.