Introduction
The contents of the map view is based on the entities (workflows, simulations, executions and data) that you add to it. Whenever two entities share some data (e.g. workflows and simulations), they are connected in the map view, even if one is not in the report view.
The map view has several features to help you navigate and continue your experiment.
Click blocks in the map view to open their contents in a new tab at the relevant page (e.g. click a simulation to open it in the Simulation Details page).
Add new blocks to manipulate and view data associated with the executions in the experiment.
Import existing workflows, executions and simulations.
Open the map view
You can open the map view from two pages.
If the experiment is already open, from the report view, click Report, then Map.
If the experiment is not open, from the Experiments list, click the map icon to open the map view.
The anatomy of the map view
The map view includes a map of the experiment (the experiment map), a set of controls to manage what the map displays (in the upper-left of the page), and a set of view controls (in the lower-left of the page).
The map contains blocks which represent workflows, snapshots, simulations, executions and data processing applications.
The map has clickable areas to allow navigation to the relevant parts of the interface. Click the title of a block to open the corresponding page in a new tab.
Control what you see
Use the map controls in the upper-left to perform three actions: add data processing blocks, import workflows, simulations and executions, and filter the view.
Create a data processing block
The first button on the left (Add new block) adds a new data processing block. Data can be processed either from executions or other data processing blocks.
Click the Create (+) button to choose the type of block you want to add.
Note: If only executions are present, you can only add the Align block.
Select one or more inputs, then click create to create the new block.
The new block appears in the INITIAL state. Navigate to it to select a visualization from which to download data.
To learn how to use the experiment map to process data, click here.
Import a workflow, simulation or execution block
Use the second control menu button (+) to import workflow, simulation and execution blocks.
Use the list that opens to select the entity that you want to import.
The new entity will appear as a block in the map view, along with all the other connected ones.
If you import an entity into the map view, Synthace adds them to the Report view as well, but without the related entities.
Filter failed simulations
If you add a workflow to an experiment, the map view automatically finds all of the simulations that you have created from that workflow.
Since there could be many failed simulations, Synthace hides them by default.
Click the third control to toggle whether or not failed simulations (and their parent snapshots) appear in the map.
Tip: The last selection for any given map will be remembered, so you should see the same set of simulations every time you return to the map.
Hide blocks
If you want to remove one or more blocks from the view, click them to select and highlight them.
Press delete or backspace on the keyboard to hide the block and its descendants. Synthace asks you to confirm your choice.
Note: Hiding is a property of the map, not the underlying entities. Therefore if you import a hidden entity or one of its relatives into a different experiment, then previously hidden blocks will again be visible in the map view of that experiment.
Restore hidden blocks
Use the filter menu to restore hidden blocks to the view.
Click EDIT to reveal all the previously hidden blocks. Synthace adds an ‘eye’ icon to each one so that you can toggle its visibility on or off.
Note: Blocks cannot be made visible independently: all of the connections between any two visible blocks will also be visible. Restoring a block also restores any connected blocks to follow this rule.
Experiment maps
An experiment map is a visualization of an experiment. It shows the entities that you have added directly to the experiment, and their relationships to other entities. Relationships are defined by use of data as described in the table below.
Entity Type | Used By |
Workflow | Snapshot |
Snapshot | Simulation |
Simulation | Execution |
Execution | Data Processing |
Data Processing | Data Processing |
The map is created by a search process which starts at each of the entities that are part of the experiment, and finds everything to which each entity is connected.
For example, if we add an execution to the experiment, the map will show the parent simulation, the snapshot, and the workflow that we used to generate that execution.
Similarly, if we were to add the simulation, but not its execution, the map would still show the same representation.
Adding a workflow to an experiment will cause all its descendant simulations to also appear in the map, along with any further downstream entities such as executions or data processing blocks. If the workflow is not directly imported to the map or added to the report view, then other simulations will not be automatically added to the map.