Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine which variables need to be kriged and apportioned in final reporting #219

Closed
leewujung opened this issue Mar 31, 2024 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation FEAT high_priority

Comments

@leewujung
Copy link
Member

The Matlab code contains multiple different options for kriging and apportioning different variables.

Our current understanding is documented in this block diagram:
https://docs.google.com/presentation/d/1FOr2-iMQYj21VzVRDC-YUuqpOP0_urtI/edit#slide=id.p1

The boxes highlighted in red have been implemented (despite questions such as #217, #42, #183).

The goal here is to determine which variables need to be kriged and apportioned in final reporting.

@leewujung leewujung self-assigned this Mar 31, 2024
@leewujung leewujung added the documentation Improvements or additions to documentation label Mar 31, 2024
@leewujung
Copy link
Member Author

leewujung commented Apr 14, 2024

Conclusion from meeting with RT on 2024/04/01:
We will stay with the red boxes in the slide that have already been implemented in Echopop -- kriged biomass and kriged abundance.

New question for 2024/04/15:
We found out that the kriged abundance apportioning in the matlab code does not apply the age bin mapping from the aged fish samples to the unaged fish samples, but this was done for the kriged biomass apportioning. Is it useful to apply the same mapping to get to equivalent outputs as the kriged biomass?

The new question is tracked in #224, so I'll close this now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation FEAT high_priority
Projects
Status: Done
Development

No branches or pull requests

1 participant