Conversation
Member
I'd say it is, because the observable isn't used anywhere. If there was a measurement, the linter would complain. I don't know if the extra observables or the missing measurements are the real issue here. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I don' think this is valid PEtab. The spec does not explicitly state that
${observableId}innoiseParameter${indexOfNoiseParameter}_${observableId}has to match the corresponding observableId. However, as the noise parameters have to be specified in the measurements table and you can only specify the noise parameters of the corresponding variable in the measurements table, I don't see any way how this would be valid.Also, how did nobody ever spot this 😅.