Decouple metering from bwc field #20

Closed
opened 2024-04-09 09:29:17 +00:00 by Patrick Vogler · 1 comment

The metering option should only be used if profiling is done by the user. Therefore the meter substructure in bwc_field should be moved into a separate type def and added to the code through a pre proc directive. Codestream Size and other vlues necessary for (de)compression are to be added to bwc_gl_inf.

The metering option should only be used if profiling is done by the user. Therefore the meter substructure in bwc_field should be moved into a separate type def and added to the code through a pre proc directive. Codestream Size and other vlues necessary for (de)compression are to be added to bwc_gl_inf.
Patrick Vogler self-assigned this 2024-04-09 09:29:17 +00:00
Gregor Weiss was assigned by Patrick Vogler 2024-04-09 09:29:17 +00:00
Patrick Vogler added this to the Interfaces project 2024-04-09 09:29:17 +00:00
Patrick Vogler removed their assignment 2024-04-09 10:19:33 +00:00
Gregor Weiss was unassigned by Patrick Vogler 2024-04-09 10:19:33 +00:00
Collaborator

I am looking into this because I am looking into the data structures for GPU porting.
Extracting metering is straightforward. Otherwise bwc_field packages tile, global info, and control. I think it would be ok to preserve this packaging as bwc_field.

I am looking into this because I am looking into the data structures for GPU porting. Extracting metering is straightforward. Otherwise `bwc_field` packages tile, global info, and control. I think it would be ok to preserve this packaging as `bwc_field`.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: TOPIO/BigWhoop#20
No description provided.