CliMA / CliMA/ParameterEstimocean.jl
Separate components of EKI objective functional?
- Dominant language
- Julia
- Stars
- 22
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
It might be more convenient to provide the components of the eki objective functional separately rather than tupled toghether as in:
https://github.com/CliMA/ParameterEstimocean.jl/blob/8e571182f4bf385e83ea7e4ab052c473a76b9016/src/iteration_summary.jl#L96
@adelinehillier what are your thoughts?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with src/iteration_summary.jl around line 96, where the EKI objective functional is linked in the issue. Read the surrounding summary API and determine how its components are currently tupled. Done means providing those components separately with a clear interface, while preserving the intended objective summary behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100