Data, Project and Export
The main project stores the task being edited. Images, method results, and representations for other tools are stored next to it as separate files.
What is included in the project
The main project stores the task’s editable data. You can regenerate materials for code and other tools from these data. Save handwritten code and recordings separately; they are not included in these materials automatically.
- Format version, program mode and task settings.
- Elements, features, regions, relationships, groups and annotations.
- Links to source images and attached computer vision results.
- Information needed to check the project structure and linked files when opening it.
Files next to the project
An export fixes the selected state at the time it is prepared. Later project changes do not automatically update a copy that has already been shared: save your changes and prepare a new export.
| Material | Purpose |
|---|---|
| Source images and frames | Visual materials on which the markup was created. |
| Operation results | Masks, outlines, detections, recognized text, metrics and execution details. |
| Code view | Selected task data for Screph Code or a supported external tool. It does not replace the main project. |
| Automation script | A separate code file that uses the main project when explicitly running Automation Runtime. |
Computer vision results
Previewing or temporarily running an operation does not change the main annotations. You can attach its result to the project. A proposed change to an element or feature requires review and confirmation.
When you save a project, only the materials that are associated with the project by the selected workflow are copied. The remaining temporary results remain in the local data directory and are cleaned up separately.
Transfer and backup
If another program or another Screph instance has changed a file, do not overwrite it blindly. Save both versions separately, close extra instances, and open the copy you need. Autosave and editing history do not replace an independent backup.
- Save the project and wait until the files are written.
- Copy the entire project directory along with images and attached results.
- Open the copy from the new location and check for warnings about missing files.
- If your project uses a separate script or working code folder, save them separately.
Coding and Execution
Updating prepared materials can conflict with manual file edits. If a conflict is reported, save your version first and compare the contents. Saving the project does not undo changes in a separate code workspace folder.
- Screph Code gets the selected data view and can modify the files in the working directory.
- Automation Runtime opens the main project and a separately prepared script.
- Passing data does not run code or dispatch input actions automatically.
Before handing over the project
- Prepare a separate copy for sharing and exclude unnecessary images, logs, keys, personal data, and experiment results while retaining the files the project needs.
- Check the licenses of the source materials and models.
- Open a copy of the project and make sure all the necessary files are available.