donders-institute / dicom-dataflow Goto Github PK

so that data can be re-transferred upon failure or service downtime

subject has max. 3 digits
session has max. 2 digits

Assuming the LUA function onStableSeries is failed on certain series, the system admin should be able to rerun the transfer manually using a standalone script.

• what is the setup AFTER data-streamer?

• how permissions across ppl are managed etc

• how data is standardized into BIDS and QC scripts are ran
  (Arjen said that he things BIDS'ification of MRI data is automated)

Either make the LUA script to work with email notification; or should monitor the errors in 'log/Orthanc.log' in a more proactive way.

Hi @hurngchunlee, browsing through the list of github repos on donders-institute, I noticed the inconsistent naming. Would you mind renaming this one from DCCN-xxx to xxx? it being part of donders-institute should be sufficient that it is specific to our research site. It also makes it more consistent with hcp-wiki and torque-monitor.

This behaviour will eventually cause some series being ignored in the data flow. For example, the series is not considered as "stable" before the restart; but there is no more in-coming data from the scanner.

is it the endpoints configured in https://github.com/Donders-Institute/dicom-dataflow/blob/master/docker/cal2wl/config/config.yml

NB Extract from an email correspondence

NB Extract from an email correspondence

• orthanc server -- it is just used as a PACS to receive data and
  is not accessible to individual researchers?

is it accessible to MR tech to e.g. review the data which was sent, or
just the data as moved by STREAMER is available for review in "project
storage" or "archive"?

overall - how MR tech could review some prior acquired data?

Currently the token is initialised with a fresh one-time password at the time the "stager" service is started.

The service assumes there will be continuous activity during the operation, and thus the token gets extended.

However, if there is no activity for a week, the token can just expire silently; causing the upcoming activities to fail.

This should be addressed.