Opened 17 years ago
Closed 16 years ago
#340 closed task (fixed)
Experiment validation tool
Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
---|---|---|---|
Priority: | minor | Milestone: | BASE 2.2 |
Component: | coreplugins | Version: | |
Keywords: | Cc: |
Description
The core is very loose when it comes to checking the structure of linked items. For example it doesn't care about the number of labeled extracts that are linked to a hybridization or if the labels are different. A sanity check tool would for a project and/or experiment check a lot of things and output a list of warnings. Here are some more example of what could be checked:
- The project defaults are used (see #334)
- Annotations have been specified for all items
- Inherited annotations are from parent items
The validation tool may have some common points with #262: Overview of an experiment
Change History (9)
comment:1 Changed 17 years ago by
Milestone: | BASE 2.x+ → BASE 2.2 |
---|
comment:2 Changed 17 years ago by
Priority: | major → minor |
---|
comment:3 Changed 16 years ago by
Status: | new → assigned |
---|
comment:4 Changed 16 years ago by
comment:5 Changed 16 years ago by
comment:6 Changed 16 years ago by
comment:7 Changed 16 years ago by
comment:8 Changed 16 years ago by
comment:9 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
(In [3024]) References #262 and #340. Added draft specification