Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
biac:pipeline [2019/05/07 14:54] – cmp12 | biac:pipeline [2022/11/18 16:08] – external edit 127.0.0.1 |
---|
| |
| |
| ===== Backup Workflow ===== |
| |
===== Backup Daemon Flowchart & Backup Admin Workflow ===== | A nightly cron job copies locally processed and raw data from the AIMS computers to a network attached storage location. This includes all k-space data, pfile headers, nii.gz data, physio files, etc. |
| |
{{:biac:backup.png|:biac:backup.png}} | |
| |
| On a monthly basis the archives are moved to a cloud based S3 cold storage location hosted by Duke. |
| |
===== User Frequently Asked Questions ===== | ===== User Frequently Asked Questions ===== |
| |
=== How does the pipeline assign a dataset to an Experiment? === | === How does the pipeline assign a dataset to an Experiment? === |
For functional data, the Patient ID that is entered on the scanner console is primarily used for identification. Our software takes what is entered in on the console, strips out the punctuation, and lowercases all text before before comparing against a list of valid Experiments. | For imaging data, the PatientID and ExperimentID that is entered on the scanner console is primarily used for identification. Our software takes what is entered in on the console, strips out the punctuation, and lowercases all text before before comparing against a list of valid Experiments. |
| |
===The tech entered the correct Experiment ID on the 4.0T console, but the dataset was not properly assigned to an Experiment. What happened? === | ===The tech entered the correct Experiment ID on the scanner console, but the dataset was not properly assigned to an Experiment. What happened? === |
If you entered a period in the Patient ID field, GE's software seems to have a bug in which the characters following the period are truncated before being inserted into the raw data header. As a result, the truncated Patient ID is unrecognized and the image results gets transferred to the Salvage directories. This only applies to functional data from the 4.0T. | If the ExperimentID entered on the scanner does not match a list of valid Experiments, or that Experiment's storage location is full, then our processing daemon will temporarily transfer data to our Salvage.01 experiment location. You can file a trouble ticket to get assistance receiving the salvage data. |
| |
===How do I check the status of my data?=== | ===How do I check the status of my data?=== |
Under the 'Services' page on the BIAC website, click on 'Exam Tracker' and enter your 5 digit exam number. If the processing daemon has picked up and processed the files, you'll see the relevant log information. | You can look at our status monitor page and select Exams -> Exam Number under the appropriate scanner which will display which series have been processed. Also you can check your experiment location on the BIAC 'Exam Tracker' page to see similar information and various QA measures. |
| |
===I see errors on the Exam Tracker page and my data did not show up. What do I need to do?=== | ===I see errors on the Exam Tracker page and my data did not show up. What do I need to do?=== |
If the error you see is 'Experiment Not Found', please submit a trouble ticket so our data administrators can know where the data was supposed to be sent. Our data admins will respond as soon as possible to the trouble ticket. | If the error you see is 'Experiment Not Found', please submit a trouble ticket so our data administrators can know where the data was supposed to be sent. Our data admins will respond as soon as possible to the trouble ticket. |
| |
Looking for the [[biac:pipeline:adminfaq|Pipeline/Data Administration FAQ]]? Restricted. Request access by sending an email to Josh or Jimmy. | Looking for the [[biac:pipeline:adminfaq|Pipeline/Data Administration FAQ]]? Restricted. Request access by sending an email to Josh or Chris. |
| |
| |
| |
| |
| |