NDTS Experiment Harvesting: Difference between revisions
From Network for Advanced NMR
Jump to navigationJump to search
Mmaciejewski (talk | contribs) No edit summary |
Mmaciejewski (talk | contribs) |
||
| Line 5: | Line 5: | ||
* '''VNMRj''' - the daemon listens to InfoProc network messages to detect transitions in status (e.g. idle to acquiring) | * '''VNMRj''' - the daemon listens to InfoProc network messages to detect transitions in status (e.g. idle to acquiring) | ||
* '''TopSpin 3.x''' - the daemon uses inotify (ReadDirectoryChanges on Windows) to monitor changes to the accounting file | * '''TopSpin 3.x''' - the daemon uses inotify (ReadDirectoryChanges on Windows) to monitor changes to the accounting file. See additional details on how NDTS utilizes the TopSpin accounting file [[Monitoring TopSpin Accounting File|here]]: | ||
** accounting must be enabled on a per user basis | ** accounting must be enabled on a per user basis. See [[Enabling TopSpin Accounting|enabling TopSpin accouting]] for more details. | ||
** only detects experiment end events. The experiment start time is determined after the experiment is complete | ** only detects experiment end events. The experiment start time is determined after the experiment is complete | ||
* '''TopSpin 4.x''' - the daemon monitors the shmem file in the user-specific TopSpin directory for start and end events | * '''TopSpin 4.x''' - the daemon monitors the <code>shmem</code> file in the user-specific TopSpin directory (<code>{topspin_directory}/prog/curdir/{user}/shmem</code>) for ''start'' and ''end'' events | ||
== Sessions == | == Sessions == | ||
Revision as of 17:45, 9 June 2025
Overview
Identifying acquisition start and end events
The daemon detects when TopSpin or VNMRj is launched, who launched it, and whether it controls the spectrometer. How experiment start and end events are detected varies depending on the software version controlling the spectrometer:
- VNMRj - the daemon listens to InfoProc network messages to detect transitions in status (e.g. idle to acquiring)
- TopSpin 3.x - the daemon uses inotify (ReadDirectoryChanges on Windows) to monitor changes to the accounting file. See additional details on how NDTS utilizes the TopSpin accounting file here:
- accounting must be enabled on a per user basis. See enabling TopSpin accouting for more details.
- only detects experiment end events. The experiment start time is determined after the experiment is complete
- TopSpin 4.x - the daemon monitors the
shmemfile in the user-specific TopSpin directory ({topspin_directory}/prog/curdir/{user}/shmem) for start and end events
Sessions
Datasets that are skipped automatically
NDTS Audit File
The NDTS audit file will show detailed records of every dataset that the daemon detected and what what the status of the transfer is (e.g. sent, spooled, skipped).
What is harvested
What if gateway is unreachable
Limitations
NDTS is off
paropt
missing critical data
