Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Development Prioritization: Figures

Aperta
  • Qualcosa non va?
#2 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
r
Ambito
data-visualization

Direzione di ricerca

Inizia dall’elenco delle figure proposte nell’issue e ispeziona la cartella R per determinare quali elementi P2 non selezionati e quali elementi con la priorità più bassa dispongano già di funzioni corrispondenti. Il documento di prioritizzazione collegato richiede l’accesso interno a NOAA, quindi conferma l’ambito e i criteri di accettazione prima di implementare qualsiasi figura o una funzione comune di plotting. Il lavoro è completato quando le figure selezionate sono implementate e i relativi elementi della checklist possono essere contrassegnati come completati.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

development enhancement

Coding in Figures

Each of the proposed figures in the list below will be coded in as function in the R folder. I am thinking additionally there will be a function that will plot common figures together based on their categorization or type of data they are plotting.

Determining Rank

The tables and figures proposed and reviewed by the steering committee were prioritized based on the number of votes they each table or figure received. The different between positive and negative votes determined rank. Objects with a difference above 3 were categorized as P1. Below 3 but equal to or greater than 0 were designated as P2, and anything below a zero was designated as parking lot. Objects ranked at 3 were decided either to be P1 or P2 depending on comments and the developers expertise. Objects within the rank were listed in descending order of difference and objects with the same value were placed in order based on developer expertise.

The proposed list of tables and figures can be found here.
*Note: Only NOAA internal employees can access this document.

Guide:

P1: revived the highest amount of votes from the steering committee and are incorporated into almost every stock assessment used for management advice
P2: medium priority items that are important but can pushed a little bit later in development
“Parking lot”: lowest priority for development; will still be added into the package for the first release, but is not needed as soon as the other tables; received lowest amount of votes/negative votes

() = category
D = data
ES = executive summary
AM = assessment mode
P = projections

High Priority (P1)

  • Landings (D): Cumulative area time series plot; by fleet
  • CPUE indices (D): Line graph with CIs; strat. By survey/fleets
  • Estimated recruitment (AM): line graph with error bars
  • Biomass time series (ES & AM): Line graph with biomass reference point as horizontal dashed line
  • Spawning biomass time series (AM): line graph

Medium Priority (P2)

  • F or exploitation rate time series (ES): Line graph; F reference point as dashed line
  • Recruitment deviations time series (AM)
  • Kobe plot (ES): base model and any sensitivity models (most likely only base model)
  • Model fit to abundance (N) or fishing effort (AM)
  • Projections (P)
  • Model fit to catch time series (AM): Line graph?; by fishery and/or gear
  • vonB length at age (D): Points + line graph for model fit; potentially stratified by area, gender, ect.
  • Catch at length (D): Histogram; by year, fleet, or FI survey

Lowest Priority

  • W/L conversion (D): Points + fitted curve, R sq. value and eqtn
  • #62
  • #60
  • Maturity schedule (D)
  • #68
  • #66
  • Fecundity at age (D): if applicable
  • Catchability (q) time series (AM): line graph; only if time varying
  • Length type conversion (D): Ex: TL to FL; raw points with linear fit, R sq. value, and resulting eqtn.
Lingua principale
R
Stelle
20
Fork
8
Merge medio
20h 52m
PR unite (30g)
10

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nmfs-ost/stockplotr

Tutte le issue di nmfs-ost/stockplotr

Issue simili

Altre issue su R

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.