Desired Input Validations

Page is outdated / Marked outdated on May 22, 2020

Some associated (also outdated) documentation can be found in the DataStructures_README.md

This covers some of the basic discussions which revolved around variables, actions, and general capture ideas back in July 2019. Many of these plans will be updated or have evolved for ESCALATE v3.

Input Validation

• Variable assertions for types indicated in input form (ensure vales of the correct type)
• Variable inspection for ranges and thresh holds.
• Variable structure enforcement --> ensure structure is as expected
• exp1 (or 2,3,etc) exp1_vols should have the same number of lists

Specific Input Constrain Notes (combinations of inputs that should flag errors)

• ExpWorkflowVer = 3 should only be used with LBL
• ExpWorkflowVer = 3 should not have wellcount > 24
• ExpWorkflowVer = 3requires exp*_split defined
• ExpWorkflowVer = 3 should not use more than 1 experiment
• ExpWorkflowVer = 3 Split must be same reagent as final specified portion in exp1 (2,3, ect)

Capture_report Dataframe validation

• Only one value in each _InChi_Key String
• Report code returns dataframe with desired headers (schema is needed here)
• Contents of JSON including

Suggested System Tests

• Stateset can be generated for experiment 1 using any combination of reagents. This would be test that requires as much time to run as single execution, but values should remain the same if the inputs are the same. The ground truth can be generated once and then tested against future versions of the code.