[BUG] Fix nargin check #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* First varargin is scoped when nargin==6 * Set default invEFF to 0.96 (based on Demos) * Minor syntax clean up
|
@agahkarakuzu, I'm quite certain that @JosePMarques doesn't want to ignore the data folder, as it is key for his examples. Since this is mostly a static repo, the data was uploaded once and will never change again, so something like OSF would be overkill for here. |
Sounds like another good reason to ignore tracking I just did it for the sake of good practice, happy to revert at @JosePMarques's discretion. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
T1B1correctpackageTFL.mregarding argument parsing, corrected in d53a92b..gitignore