User feedback indicates that CSV output currently makes it difficult to achieve desired external analysis goals.
Desired format is a time-ordered list of activities, with power and comms consumption tracked for each row.
Given that activities may overlap (or contain subactivities) some design is necessary to determine the most useful output format for these. It may be useful to allocate one row for every change in the set of current activities in that time-ordered list.
Currently, CSV export simply dumps the Info View of contained objects. This is nice because it generalizes; the improved output described here may be something that makes more sense as a separate feature.
152 and #157 provide some of this capability, but there is still significant work required to massage CSV formats down to the desired information.
User feedback indicates that CSV output currently makes it difficult to achieve desired external analysis goals.
Desired format is a time-ordered list of activities, with power and comms consumption tracked for each row.
Given that activities may overlap (or contain subactivities) some design is necessary to determine the most useful output format for these. It may be useful to allocate one row for every change in the set of current activities in that time-ordered list.
Currently, CSV export simply dumps the Info View of contained objects. This is nice because it generalizes; the improved output described here may be something that makes more sense as a separate feature.
152 and #157 provide some of this capability, but there is still significant work required to massage CSV formats down to the desired information.