Open mtbannister opened 10 years ago
this ‘feature’ is caused by how I implemented auto loading of data frames to smooth the activities of blinking.
JJ
On 10-Feb-2014, at 11:38, Michele Bannister notifications@github.com wrote:
A small inconvenience. After changing between .astrom.reals files, 'reals' ds9 window shows blank white: starting blinking with tab or 'd' autoplay then shows the second image of the triplet correctly. The first image is there correctly when the triplet cycles around.
So not a problem for assessing the triplet, but a bit puzzling.
— Reply to this email directly or view it on GitHub.
No worries.
having the ‘reals’ process have its own on_next method in the realsValidation sub-class would likely work to solve this… or something like this. Search for prefetching in the controller.
jj
On 10-Feb-2014, at 14:12, JJ Kavelaars jjkavelaars@gmail.com wrote:
this ‘feature’ is caused by how I implemented auto loading of data frames to smooth the activities of blinking.
JJOn 10-Feb-2014, at 11:38, Michele Bannister notifications@github.com wrote:
A small inconvenience. After changing between .astrom.reals files, 'reals' ds9 window shows blank white: starting blinking with tab or 'd' autoplay then shows the second image of the triplet correctly. The first image is there correctly when the triplet cycles around.
So not a problem for assessing the triplet, but a bit puzzling.
— Reply to this email directly or view it on GitHub.
A small inconvenience. After changing between .astrom.reals files, 'reals' ds9 window shows blank white: starting blinking with tab or 'd' autoplay then shows the second image of the triplet correctly. The first image is there correctly when the triplet cycles around.
So not a problem for assessing the triplet, but a bit puzzling.