[Feature Request] about beep HOT 4 CLOSED

@ardunn Yes, the required name should be something like cycle_index. Most of the internal mapping ones are not used in the structuring process.
A: For this we only care about being able to create a ProcessedCyclerRun object
Yes, I think that data_point is not actually required for any of the processing. Likewise, I think that step_time is not actually used by any of the functions

from beep.

Ok I will systematically try removing columns from the test case and see when ProcessedCyclerRun fails. I'll list all the columns for completeness and mark the required ones as "required"

from beep.

beep/conversion_schemas has a lot of the columns necessary to run the structuring so

from beep.

@patrickherring-TRI by "standardized name" you mean the required name (has_special) and not the internal mapping (_has_special), correct?

Also, for necessary, does this mean:

• A: Able to create a ProcessedCyclerRun object in structuring
• B: Able to Validate?
• C: both A and B?

It seems like the only column headers necessary (at least for Arbin) are defined in the validation schemas - things like data_point aren't required(?) for validation or structuring?

from beep.