DataMind Oda keeps the settings it saves and the caches it builds on your computer inside one home folder. This page shows how Oda chooses that folder, how it shows the location, and what keeps a settings save safe.
Oda uses the first of these that is actually set:
~/ <folder>, where ~ stands for your user folder. A home you set yourself is shown by the name of the setting you used.When Oda saves a settings file, it does not rewrite the file in place. It works in three steps:
Two more behaviours you may meet:
For what the settings file contains and when you may edit it, see The profile settings file.
If the wait for the lock runs out, the save does not happen, and Oda reports that it timed out waiting for the writer lock, naming the lock file's path. Try the change again. If it keeps failing, follow Updates and troubleshooting.
Do not delete a lock file yourself. Removing a lock that a crash left behind is done as a careful step, only after confirming that no writer still owns it. Ask DataMind support.
Oda reads its start values from three places, in order:
A value from a higher place wins over one from a lower place. Oda takes this snapshot once, when it starts, so a later folder change does not affect the run in front of you.
A settings file cannot make Oda treat a run as an SSH run. Oda decides that from the environment it was launched in, never from a settings file. See SSH remote execution. The full rules for these files, including the values a file may not set, are on Startup and diagnostics.
By default it is a folder inside your user folder; it can also be chosen for the run or named in the environment Oda starts in. The settings files Oda saves and the caches it builds live under it. Oda shows the location in a short form, never the full path.
Yes. Name the folder you want in the home setting of the environment you start Oda in, and Oda uses it the next time it starts. A blank or spaces-only value is ignored, so an empty setting moves nothing. The caches Oda builds live under the folder as well.
Oda writes the home folder in a short form such as ~/, where ~ stands for your user folder, and a home you set yourself is shown by the name of the setting you used. The full path on your computer is never written into what Oda shows you.
Another save was in progress, or a crashed writer left its lock file behind. Try the change again. If it keeps failing, do not remove the lock file yourself; follow Updates and troubleshooting.
No. Oda writes the new content to a temporary file beside the target and renames it over the target in a single step, so a reader sees the old file or the new one. A save that fails removes its temporary file and leaves the settings file as it was.
The settings file holds the old content or the new one, never something half-written. The lock file can survive the crash, and later saves then wait for it and time out until it is removed. A sudden power loss is the one case Oda does not cover: the replacement is not flushed for it, so the very newest save can be lost.
It reads them in order: the environment Oda is launched with, then a settings file in the folder you launch from, then a settings file in the home folder. A value from a higher place wins over one from a lower place.
Oda takes its snapshot of these values when it starts, so a later folder change does not affect the run in front of you. Start Oda again from the new folder to use its values.
No. Oda treats a run as remote only when the environment it was launched in says so; a settings file cannot establish an SSH session. See SSH remote execution.