[Feature]: Multivariate-Tweedie for age/length compositional likelihood
@iantaylor-NOAA ci sta già lavorando.
Dal 7/3/2022.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
I'm leading a paper with Tim Miller and Brian Stock, introducing a new "multivariate-Tweedie" likelihood for fitting age/length composition data. It is essentially a more flexible alternative to the Dirichlet-multinomial, and appears to have some useful pros and cons relative to the DM. It internally relies upon a dtweedie likeliood, which Johnoel is adding the ADMB-13, so it should be feasible to implement in SS3 by this summer.
Does anyone have sufficient time and interest to work with me to get it implemented (both in logical code, and with a thoughtful user-interface) in SS3?
[Edit: task list below added by Ian on March 24.]
To-do list for MV Tweedie likelihood based on comments above:
- create new MV-Tweedie-complike branch to host changes code
- add new likelihood calculation to
SS_objfun.tpland create a pull request (#278) - wait until ADMB 13 is released which will include the
dtweediefunction: https://github.com/admb-project/admb/issues/234 - double check likelihood calculation added to
SS_objfun.tplby @James-Thorson-NOAA - see what parameters need to be created in
SS_readdata_330.tpl - name parameters in
SS_readcontrol_330.tpl(two for mvtweedie compared with one for DM) - check everything else is handled automatically (reporting and write_ssnew)
- document the changes in the SS3 User Manual
- generalized size frequency section already updated in https://github.com/nmfs-stock-synthesis/doc/commit/28dd822037c4bfa1d04ad76a9f8a3972b7e7aece
- apply any parallel changes to DM likelihood (discussed in #185 and #219)
- modify r4ss to work with models that use MV Tweedie
- Lingua principale
- C++
- Stelle
- 46
- Fork
- 19
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di nmfs-ost/ss3-source-code
-
composition in progress
nmfs-ost/ss3-source-code#751 · 1 commento · 1 assegnatario ·
-
area & movement
nmfs-ost/ss3-source-code#731 · 3 commenti · 1 assegnatario ·
-
misc. output
nmfs-ost/ss3-source-code#723 · 1 assegnatario ·
-
biology misc. output ongoing
nmfs-ost/ss3-source-code#702 · 1 assegnatario ·
-
recruitment
nmfs-ost/ss3-source-code#696 · 1 assegnatario ·
Tutte le issue di nmfs-ost/ss3-source-code
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
duckdb/duckdb-wasm#2258 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
objectionary/eo-graphs#75 ·
-
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Apertacoarray
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
FISCO-BCOS/FISCO-BCOS#5642 ·