Support to specify the range and resolution of parameter spaces #5
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.
Commit 1. The hard-code mapping function is replaced by the mapping function based on specific parameter spaces defined by users. The original hard-code mapping function can be regarded as the mapping function of the parameter space with special ranges and resolutions, which are served as the default values of the new mapping function.
Commit 2. The peak sensitivity space and peak frequency space should be subspaces of stimuli spaces (1/contrast, frequency). Thus, a simple parameter validation is added to check whether the range of peak sensitivity is smaller than the range of 1/contrast. For example, the range of contrast (0.01, 1) corresponds to the range of sensitivity (1, 100). However, it is too small for searching the value of peak sensitivity in the range of (2, 1000).