459 bug show allowed deviation fields for cl validation#460
Open
AnnaPolensky wants to merge 2 commits into
Open
459 bug show allowed deviation fields for cl validation#460AnnaPolensky wants to merge 2 commits into
AnnaPolensky wants to merge 2 commits into
Conversation
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||
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
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.
Description
Fixes #459 (same issue as #455).
Also, adds the missing connections in the cl_monomer workflow (#454 )
As soon as you have uploaded some crosslinking data the fields for entering manual bounds are displayed.
Testing
Create a cl_monomer workflow. Check that the connections look like this:

Upload some cl data and check that you can enter an upper and lower bound for the accepted validation as soon as you switch to the validation step.
PR checklist
Development
Mergeability
blackpnpm formatand checked withpnpm lintCode review