Skip to main content

FAQ

What is the difference between a namespace and a volume?​

A namespace is ground-side storage and the organizational boundary for operations, executions, uploaded files, and downlinked results. A volume is an onboard storage location selected by a task. An uplink copies namespace files into a volume; a downlink copies selected volume files back to a namespace. A pod mounting payload sees that volume at /data.

Why is a requested file missing?​

Check the task's volume and exact path first. For pod output, write the result under /data, not an ephemeral container path. A fisheye task and a downlink are separate steps: a successful fisheye task alone does not put a file in the ground namespace, establish that a fresh exposure was produced, or guarantee a timestamp.

An explicit empty files result means that no file was uploaded for that downlink. It is different from a missing task result, which should be treated as a task or transport problem. Verify source paths, the selected volume, and the namespace destination before retrying.

Should I use EM or FM?​

Use the Engineering Model (EM) to validate an operation before requesting a Flight Model (FM) run. FM execution and cancellation are operational requests with uplink/downlink constraints; cancelling in the dashboard requests cancellation and does not guarantee an already-uplinked run can be stopped.