|
| 1 | +# Code and data arrangement |
| 2 | + |
| 3 | +## Version control |
| 4 | + |
| 5 | +In the lab we (try) to stick to version control for code with git/github and data with datalad and gin. Somewhere else is already mentioned but repetita iuvant so |
| 6 | +1. Install git on your computer |
| 7 | +2. Create a GITHUB account and ask to be added to the lab organization [https://github.com/cpp-lln-lab] |
| 8 | +3. Make sure you have your SSH key for GITHUB following this tutorial |
| 9 | +4. Have a look at this doc to have a first idea on how to contribute on github |
| 10 | +5. Have a look around cause we already have a lot of ready to use code ;) |
| 11 | +6. Make sure you are set up with the following tools having a look at this doc’s first section |
| 12 | + 1. Datalad (in a nutshell git for data but checkout more here https://handbook.datalad.org/en/latest/) |
| 13 | + 2. Gin (host server for data, good for “unlimited” and free cloud back and private and public data sharing) |
| 14 | +7. Ask to be added to the Gin organization of the lab to start storing your data there |
| 15 | + |
| 16 | +## Data management |
| 17 | +for MRI data the lab is moving towards using the BIDS data structure |
| 18 | +* bids starter kit |
| 19 | +* bids specification |
| 20 | + |
| 21 | +### Official GIN/DATALAD CPP dataset organization |
| 22 | + |
| 23 | + |
| 24 | +[WIP] Checklist to make an official “raw” repo (bids, bids-validator checked, standard CPP data organization (eg group naming, task naming, readme with link to published/preprint, etc)) |
| 25 | + |
| 26 | +[WIP - Just dropping useful links here for now] |
| 27 | + |
| 28 | +Data: |
| 29 | + |
| 30 | +Dataset summary (put together all the bidsified raw and derivatives repos of the lab and summarize metadata in a table) https://cpp-lln-lab.github.io/Datasets/ |
| 31 | +repo to edit it: https://github.com/cpp-lln-lab/Datasets |
| 32 | + |
| 33 | +main organization for "structured": data saving and conversion control and sharing with “raw” (bidsifield) and “derivatives” and “source” repos: https://gin.g-node.org/cpp-lln-lab |
| 34 | + |
| 35 | + |
| 36 | +Guidelines to maintain the CPP dataset https://github.com/cpp-lln-lab/dataset_maintenance |
| 37 | + |
| 38 | +Datalad superdataset to grab all the repo together: |
| 39 | +https://github.com/cpp-lln-lab/cpp-lln-lab_derivatives |
| 40 | +https://github.com/cpp-lln-lab/cpp-lln-lab_source |
| 41 | + |
| 42 | +Tools: |
| 43 | +https://github.com/cpp-lln-lab/template_datalad_bids-raw |
| 44 | +https://github.com/cpp-lln-lab/CPP_dcm2Bids |
| 45 | +https://github.com/cpp-lln-lab/letswave_bids_import |
| 46 | +https://github.com/cpp-lln-lab/eeg_bids_conversion |
| 47 | + |
| 48 | + |
| 49 | + |
| 50 | +## Other back ups |
| 51 | + |
| 52 | + |
| 53 | +### IONS cloud storage |
| 54 | + |
| 55 | + |
| 56 | +http://sss-intranet.icp.ucl.ac.be/wiki/index.php/Storage_access#Groups |
| 57 | + |
| 58 | +cooked step by step for MacOS users: |
| 59 | + |
| 60 | +1. Open Finder |
| 61 | +2. Go menu |
| 62 | +3. Element Connect to server |
| 63 | +4. Add address smb://sss-samba.icp.ucl.ac.be/cosy-oc |
| 64 | +5. Use your UCLouvain credentials when asked |
| 65 | +6. Add the opened folder as a favorite (top of the right panel) |
| 66 | + |
| 67 | + |
| 68 | +Short guidelines: |
| 69 | +* not suitable for an “online” usage (eg running analyses within the folder), it is a cloud service so reading and writing is as fast as your internet connection |
| 70 | +* Long term storage |
| 71 | +* Please, be organized. Imagine that another person in the future will open that folder and make sense of the content in less than 2 minutes |
| 72 | +* Add README files to help the future user understand what’s inside that folder (e.g. dicoms from the study XXX published in XXX code for conversion/analyses here github.com/xxx, copy of this dataset is also on gin.g-node.org/xxx) |
| 73 | + |
| 74 | +What to put there? Should not become a data dump so not just a new space where a user can free up her/his hard disk |
| 75 | + |
| 76 | + |
| 77 | + |
| 78 | +## Get organised |
| 79 | + |
| 80 | +### Code style guides |
| 81 | + |
| 82 | + |
| 83 | +matlab |
| 84 | +https://www.mathworks.com/matlabcentral/fileexchange/46056-matlab-style-guidelines-2-0 |
| 85 | + |
| 86 | +### Useful links |
| 87 | + |
| 88 | +A quick thread on how to organize your scripts: |
| 89 | +https://twitter.com/wmvanvliet/status/1240907591791886337 |
0 commit comments