Make datman easier to install and use#303
Conversation
Due to the fact that datman.utils.update_checklist was expecting subject IDs without the repeat/session number, these scripts were causing exceptions to be raised on checklist update when the dashboard wasnt installed.
when running without dashboard
- Started to remove hard-coded redcap config - Updated documentation on configuration and installation
|
Hello @DESm1th, Thank you for updating! Cheers! There are no style issues detected in this Pull Request. 🍻 To test for issues locally, Comment last updated at 2022-02-23 19:46:55 UTC |
Co-authored-by: Michael Joseph <josephmje.22@gmail.com>
Co-authored-by: Michael Joseph <josephmje.22@gmail.com>
|
Thanks for the feedback Mike! :) |
jerdra
left a comment
There was a problem hiding this comment.
Thanks for putting this together Dawn! Just had a few verrry minor items that could maybe be addressed in a separate PR but i thought would be worth mentioning!
| ch = logging.StreamHandler(sys.stdout) | ||
| ch.setLevel(logging.WARN) | ||
| logger.setLevel(logging.WARN) |
There was a problem hiding this comment.
Is there a reason to have varying logging set-ups across scripts?
There was a problem hiding this comment.
Nope, none at all (except in places where we add a server log handler). This is just a historical thing leftover from the days when we joe/tom/I had three different ideas about how it should be done. I've always meant to clean up these old instances where basicConfig wasnt used though
| def get_setting(key, default=None): | ||
| try: | ||
| return cfg.get_key(key) | ||
| except datman.config.UndefinedSetting as e: | ||
| if not default: | ||
| raise e | ||
| return default | ||
|
|
There was a problem hiding this comment.
should get_setting be defined in the Config object instead?
There was a problem hiding this comment.
I think there was a good reason at the time why I put it here and not in config.py, but I can't currently remember what that was. So maybe I should move it over? I'll try to job my memory on this one
Co-authored-by: Jerry Jeyachandra <jerrold.jeyachandra@gmail.com>
|
Sorry about the delay on this @DESm1th! Is this now ready for review? |
It is! |
| ln -s pip3 pip && \ | ||
| pip install --upgrade pip | ||
|
|
||
| # Install dcm2niix/v1.0.20210317 |
There was a problem hiding this comment.
Could we upgrade the version of dcm2niix here?
There was a problem hiding this comment.
Absolutely! Thanks for catching that. What version should I add here? Just the newest?
There was a problem hiding this comment.
Hey Dawn, sorry for the late reply. Yes, it would be v1.0.20211006
@jerdra Do you know if this latest version is correct or the 2019 version RE the OPT slice timing?
There was a problem hiding this comment.
its probably fine given that we don't use slice-timing for fMRI scans anyway. The diffusion scans aren't affected
There was a problem hiding this comment.
ok! I updated the version used
This pull request adds:
assets/config_templatesthat can be used by anyone who doesnt have access to our datman-config repo