Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Moving the data files and raw processing to a separate repository
See original GitHub issueI wanted to ask your opinion about moving the data files including the raw data processing workflows to a separate repository.
We maintain Corpuscles.jl (https://github.com/JuliaPhysics/Corpuscles.jl) which is a Julia package for accessing the data files provided by Particle and the data update process is manually done.
If we had a separate git repository, we could easily integrate and even automate it.
In KM3NeT we are currently discussing a similar approach for neutrino fluxes and the general acceptance of the idea is pretty good.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
No worries Eduardo
:)I certainly don’t want to trigger more work just because of a single external package. So far we simply manually check and update the data sources and it’s not a big deal at all. I will probably go ahead and automate it based on the current structure and whenever there is time or more need for consolidation I’ll refactor.Hi @tamasgal! Apologies that I then forgot this issue from you.
I tend to agree that the data files are rather connected to the package, as we digest some and produce others, and would prefer to keep things as is. This being said, I have since ages (more or less literally) a start of work to consolidate a couple of files and simplify a bit (largely what we massage into our CSV). I will try and push forward on that, though time is often against me.