`location_composition_dataset` fails on data from 2026 onward

Open Beginner friendly
  • Is something wrong?
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
julia
Domain
data

Research direction

Start with processing.jl, focusing on _add_taxa_cover!, depth_composition, and the Dim{:timesteps} construction named in the issue. Reproduce with the provided get_photo_transect and location_composition_dataset calls, then inspect how the returned data represents report_year. Done when location_composition_dataset handles data containing 2026 without throwing.

Written by the indexing model from the issue text.

Description

processing.jl hard-codes temporal_range = 1992:2025 (in _add_taxa_cover! and depth_composition) and Dim{:timesteps}(1992:2025). The API now returns 2026 data, so location_composition_dataset throws on current data.

Reproduce

using ReefMonitoring
pt = get_photo_transect("Agincourt Reef No.1")
location_composition_dataset(pt)  # errors; the data includes report_year 2026

Suggestion: derive the year range from the data, or make it an argument.

Dominant language
Julia
Stars
1
Forks
0
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-AIMS/ReefMonitoring-DataClient

All issues in open-AIMS/ReefMonitoring-DataClient

Similar issues

More Julia issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.