-
Notifications
You must be signed in to change notification settings - Fork 15
[WIP] constrast specification + uni and multivaraite issues + remove dummies #51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] constrast specification + uni and multivaraite issues + remove dummies #51
Conversation
This reverts commit 01e95eb.
change model.Steps(iStep) to model.Steps{iStep}
- Contrasts are computed for every event in each run. - Model.json files contains the information for computing the contrasts (autocontrasts) from the level:Run
This reverts commit 01e95eb.
change model.Steps(iStep) to model.Steps{iStep}
- Contrasts are computed for every event in each run. - Model.json files contains the information for computing the contrasts (autocontrasts) from the level:Run
- remove dead code - add help section - improve human readability
- makes the use of leading zeros obsolete
|
Main change added:
Minor changes:
|
- use input file validation - use absolute paths - simplify file deletion - only delete beta / T / con maps that have been used
|
OK I have tested this on a couple of data sets and it seems OK: this should be good for one final review. @mohmdrezk most of the changes are in :
see also message above. note to self: next time let's make smaller pull requests with fewer features in them and starting from a recent version of master. |
|
One thing I will do once this is merged is to double check how it runs on octave and docker |
- fix subNumber in copyRawFolder
- pmCon: fix model.Steps(iStep) to model.Steps{iStep}
…nstrast-specification
Opening a PR to make sure that all the tests will pass and prepare for merging.