Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
smurf: Nested indexing of JSA tiles within facets
The tiles within each HEALPix base resolution pixel (facet) are now numbered using the nested scheme described in the HEALPix paper. The offsets north-east and north-west from the southern corner of the facet are represented by the even (including 0th) and odd bits respectively. This, together with the previous commit, completes the action item from the JSA meeting on 2013-10-28 of applying the standard HEALPix nested numbering scheme to the JSA tiles.
- Loading branch information
1 parent
7ed1e14
commit 5a515ff
Showing
4 changed files
with
61 additions
and
18 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5a515ff
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But...... I thought we had made a decision to leave it as it was????
I'm worried that this opening the door to people attempting to use all sorts of external HPX software that may or may not be compatible with the way we want to do things. The idea was (or so I thought) that all tile-based operations should go through smurf commands (so that we have control of it all), and that using our own tile numbering scheme was a way to ensure this.
So have any minutes or anything been made available from this meeting on 28th October? I'd better read them....
5a515ff
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was felt that using the standard tile scheme would help us with internal validation of the tiling. Makes it easier for @grahambell to do tests. JSA is only going to be using SMURF and no-one else is relevant.
5a515ff
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is "internal validation"? What tests is Graham doing?
5a515ff
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Testing of the Healpix software by people within the JSA development team.
@grahambell - can I ask what testing you plan to do? The critical issues are whether the tiles abut correctly, and whether the WCS metadata associates the correct sky position with each pixel. Other things, such as equal-area pixels, heirarchical pixels, etc, seem to be very secondary concerns to me. So I'm not sure that judging the existing code by whether it is in complete agreement with another external package on such HEALPix-specific issues is that relevant. There's nothing magic about HEALPix - all we want is some way of dividing the sky up into tiles that abut easily in pixel space without any overlap, and have a describable WCS. The fact that we've adopted an HPX like system I think should be seen as a private implementation detail.
5a515ff
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And what was the reasoning for choosing nested indexing rather than ring indexing or any other indexing scheme?
5a515ff
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That one is for @grahambell to answer. I think it was based on ease of switching SMURF over from the current scheme.
5a515ff
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The minutes are here:
https://trac.jach.hawaii.edu/trac/SCUBA2/wiki/WikiJSAmeeting
But they don't go into detail or mention ring vs. nested (those are the only two). I thought that a preference had been expressed for nested, but it did turn out that nested was also the easier change because it too is based on the facet number (*N^2) and then the index within the facet after that.