Closed xzackli closed 3 years ago
Hi @xzackli , thanks for the suggestions! Here are my thoughts:
GenericMap
to be used often in common codes, so the change GenericMap
→AbstractHealpixMap
is probably transparent to most of the users.HealpixMap
. Perhaps we should still keep Map
as a deprecated symbol and then remove it in a later release.I would like to know the opinion of other users about these changes: @PerezHz, @hhgg, @giordano, @algebrato, what do you think about these changes?
If we all agree on these, we should decide how to fit them with the release schedule. Given that they are breaking changes, a new major release would be needed, but we are in fact on the edge of releasing version 3.0, so it would be ok to merge them and then release. Not sure about point 2, how are we supposed to manage the deprecations? Should we keep them alive until version 4.0 is out, or can we remove them in version 3.1?
As there is no feedback, I assume that there are no objections with @xzackli's proposal, right? I'll create a PR as soon as I can.
I have implemented the changes proposed in this issue in PR #53. I have avoided renaming readMapFromFITS
to readHealpixMapFromFITS
because I found it too long; moreover, it is easy to resolve any ambiguity in calling this function by explicitly stating the package:
Healpix.readMapFromFITS(…)
Please test it and report any issue.
This is a very questionable set of suggestions, so please feel free to close and ignore this.
GenericMap
doesn't follow the Julia convention for an abstract type, to be calledAbstractSomeType
.using
. How about HealpixMap? This is mostly because I need to write a plate caree map type at some point. Similarly, SPT uses CEA.