Skip to content

MAINT, TST: handling of larger binary dependencies #8

@tylerjereddy

Description

@tylerjereddy

As noted in the repo for the other DR (lanl/ldrd_virus_work#19), LANL does not currently fund its GitHub organization in a way that allows us to use git lfs in any practical way for repos hosted here.

Since this is an image processing-focused project, there are naturally some larger binary image assets that we'd like to have access to without having to bloat the repo by placing them under version control, so git lfs would normally be the natural solution. This came up in the review of some of the in-house MRs that stored large binary assets (for example, review comment at https://lisdi-git.lanl.gov/ldrd_dr_neat/ldrd_neat_ml/-/merge_requests/51#note_110888), and while LFS was used to deal with this internally, it clearly won't be a sustainable long-term solution for this GitHub-hosted project.

One possible solution is to host these large binary assets externally using i.e., figshare as the other project documented at lanl/ldrd_virus_work#29. For a less manual solution, https://github.com/fatiando/pooch is a popular choice in the scientific Python community.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions