add howto for registering files #654
Conversation
|
This guide is very short, or the new file was not committed. :-D |
|
Hah! Actual file now added. |
There was a problem hiding this comment.
This is a super helpful guide for how to ingest files, especially for the use case where Tiled is running and we want to register new data sets through python.
One minor thing: For the sake of completeness, I think it would be worthwhile to include a reference to the possibility of using tiled catalog register for a similar, but more granular version of tiled serve directory.
| ### Startup mode: tiled serve directory | ||
| When Tiled is started up with `tiled serve directory <directory name>`, it takes some time at startup to read the filesystem and store information in its database. For smaller implementations of Tiled, this is very convenient. However, if the file system is large, this process can take too long every time Tiled starts up. | ||
|
|
||
| In this mode, tiled also watches the folder for changes, and reindexes the entire tree when it encounters them. Again, this is fine for smaller instances, but can be too slow if the tree is large. Additionally, watching directories for changes can be inconsistent in cases where the directories are network mounted, as with `NFS` mounted file systems. |
There was a problem hiding this comment.
I believe watching only happens when passing -w or --watch as an option.
docs/source/how-to/tiled-register.md
Outdated
| if __name__ == "__main__": | ||
| asyncio.run( | ||
| process_file( | ||
| # "/tiled_storage/beamlines/8.3.2/recons/rec20240207_120550_test_no_xrays_n257", |
There was a problem hiding this comment.
May want to remove the commented file reference.
There was a problem hiding this comment.
removed, thanks
|
Commits were pulled into #661 |
No description provided.