Hi Tobias! Just wanted to report back on a Yarra installation 'issue' that I found. I followed the instructions for server configuration. Just at the end it mentions
"Finally, edit file /etc/sudoers by typing: sudo nano /etc/sudoers and adding the following lines at the end of the file (this already includes the entries for the WebGUI):"
It turns out you can really screw up your Linux system if you get this wrong. And since this file is what configures sudo privileges, it can be difficult to recover from. Apparently the correct command would be
which opens the file in the default editor, but with some checking when you save the file that the resulting /etc/sudoers file will be valid.
Part of my problem was perhaps caused by the suggestion to add to the end of the file. But at the end there is '#include'. This looks like a comment (because everything else with '#' is a comment. But apparently in this circumstance it isn't, and adding stuff after it can cause problems!
@jgalons The issue with bypassing the operator is that it's necessary to identify a time point for the data export that does not affect the clinical scans. Because while the data export is running, new scans cannot be started (so this would have a big impact). In our case, we export the data over night when no scanning is performed. Are you planning to do this in-between scans? If you have found a way to terminate RDS after the export, this might do it. However, if scans are large, this might still impact the workflow. Other question: How do you determine when the RDS process can be killed?
Regarding the yarralink sequence: You can use it for starting RDS by modifying line 57 of the source code accordingly (or, you could simply rename RDS.exe into ort.dll).
We call RDS.exe in the code as you described. To make the transfer a “one-off” process, the configuration update rule is set-up as “Only Manually”. The timing is defined in the Startup commands menu where we added the following 4 lines for connection, transfer, disconnection and process termination.
net use z: \[servername][share] [password] /USER:[username] /PERSISTENT:YES /yes
net use z: /delete
taskkill /-im RDS.exe /f
All these commands are run sequentially and yarralink is always the last “scan” in protocols requiring data transfer for specific sequences. In our experience, the “no scanning” period never exceed the time needed for transitioning between patients which can be significant in hospitals. It has never been an issue in our outpatient imaging center where the transitioning between patients is faster. On the other end we have not been transferring huge data sets like fMRI, 4D flow or DTI tractography...
Sign in to start chatting.