Pre-allocate model inputs within scatterer objects #32
Labels
performance
Performance updates
scatterer
Scatterer data object format issues, changes, and updates
TS model
Acoustic TS model issues, changes, and updates
Milestone
Currently, some model parameters (e.g. frequency) are calculated when a
scatterer
object is initialized for a specific TS model. Generally, most model inputs are re-calculated with each call oftarget_strength(...)
. Once QOL changes listed in #28 are implemented, this would result in identical results being re-calculated over and over again which will significantly increase computation times for otherwise shared variables (such as forESS
objects via #30). In lieu of caching the results and potentially creating more overhead than necessary, themodel
slot can be amended to either permanently or temporarily store shared intermediate calculations (similar to the current implementation of SDWBA with reforgedFLS
objects held for different frequency bandwidths based on the number of position matrix segments).model
slot infrastructure such that "universal" variables shared across different models are calculated upon either object generation or first-time object initializationmodel
slot infrastructure so it stores pre-calculated variables required for input TS modelsExtract
method
soscatterer
objects can be directly manipulated within looped iterations without breaking object formattingThe text was updated successfully, but these errors were encountered: