DustMaps Belong In Their Own Package #78
Replies: 5 comments 1 reply
-
|
I think the most Julian thing would be two packages that mention each other in their READMEs. If there’s close enough integration that it requires package extensions, it might not worth it though because it could be a bit of a barrier to new contributors. I don’t think the combined package would be particularly heavyweight? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, DustMaps sounds like it belongs in its own package, particularly if it is expected to be updated on a pseudo-regular basis. Whereas DustExtinction.jl, once it is mature may not need updating. |
Beta Was this translation helpful? Give feedback.
-
|
+1 for separate packages that mention each other |
Beta Was this translation helpful? Give feedback.
-
|
Whoo, first discussion thread in this repo! It's been a while since I've looked at this package. If going the two packages route, would we want to migrate |
Beta Was this translation helpful? Give feedback.
-
|
Correct. I want to take SFD98 with me. Which would be breaking. @barrettp I think there are still reasons to update the extinction curves. For example we just got new ones with GaiaXP spectra and will get better ones in the IR with SPHEREx. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Do we think that a full implementation of the python dustmaps would belong in its own package? I am interested in porting over my PR (gregreen/dustmaps#51) and am pondering contributing to DustExtinction.jl. But part of me thinks this package should be for extinction curves, and a separate package should exist for dustmaps. Happy to hear thoughts.
Beta Was this translation helpful? Give feedback.
All reactions