Difference between revisions of "Teleconference 2018-03-21"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
** after mapping a field, show we unload both from the CUDA device (i.e. call ReleaseResourcesExecution)? | ** after mapping a field, show we unload both from the CUDA device (i.e. call ReleaseResourcesExecution)? | ||
* not much point having coordinate systems in separate space, move back to fields? | * not much point having coordinate systems in separate space, move back to fields? | ||
| + | * Should FieldSelection have a mode where you except all fields except those specified? | ||
| + | ** Use case: if thresholding by a mask, no sense in copying that field from input to output | ||
Revision as of 09:36, 21 March 2018
Attendees:
New filter interface:
- change default to select all fields to map from input to output
- do we need to rethink memory management for CUDA?
- after mapping a field, show we unload both from the CUDA device (i.e. call ReleaseResourcesExecution)?
- not much point having coordinate systems in separate space, move back to fields?
- Should FieldSelection have a mode where you except all fields except those specified?
- Use case: if thresholding by a mask, no sense in copying that field from input to output
