JuliaGaussianProcesses / JuliaGaussianProcesses/KernelFunctions.jl
Things to change before making a breaking release
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 275
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
-
Renaming of multi-output related items, see
https://github.com/JuliaGaussianProcesses/KernelFunctions.jl/issues/328 and
https://github.com/JuliaGaussianProcesses/KernelFunctions.jl/issues/332 -
Change the multi output input type definitions to not have abstract types as fields. Change to something like:
struct MOInputIsotopicByFeatures{S,T<:AbstractVector{S}, U<:Integer} <: AbstractVector{Tuple{S,U}}
x::T
out_dim::U
end
-
Change
MOInputIsotopicByFeaturestoMOInputsIsotopicByFeaturesandMOInputIsotopicByOutputstoMOInputsIsotopicByOutputs -
Clean up field names in kernel structs
Add to the list as you see fit :)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issues 328 and 332, then locate the multi-output input type definitions, including MOInputIsotopicByFeatures and MOInputIsotopicByOutputs. Review the kernel structs for field names and determine the complete breaking-release cleanup; done means the requested renames, concrete field types, and field-name changes are consistently defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- machine-learning
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100