This was set up initially to share issues with this pier but in the absence of a means to send a notification to all members, please ignore any originally suggested usage. Please consider using it to suggest anything that you would like to share with us all.
Please see later note added above which overrides anything suggested/recommended below.
It may be helpful if there was somewhere that subscribers who discover some issue with a particular job after downloading the data, could advise others. This would be up to each individual should they wish to do so upon discovering something amiss. Strictly for issues related to the downloaded data so as to keep the number of posts in this thread to a minimum.
You would need to check the box on this post if you do want be notified of replies to this topic, and thereby be informed of anything newly discovered.
The catch-22 is that you would need to actually access this post first, and right now you're completely unaware of its existence. Now if those with the privileges to do so think this may be a good idea, then they could create a catch-all post and suggest that everyone has a look. Only they have the power to do that kind of thing. Each syndicate where there is more than 1 person could have the same thing.
Anyway, I've just noticed that this pier had another funny turn. This affects the last 12 Sulphur subs for job (00)1064 part of the Sadr mosaic. Although the Fits header contains the correct coordinates, the area of sky captured in all those subs is out of alignment. I have seen this occasionally before on this pier. You would be made aware of this during alignment, but I already encountered the situation where WBPP decided to use such a frame for the master alignment! Could only ever happen to me.
Clear skies. This was set up initially to share issues with this pier but in the absence of a means to send a notification to all members, please ignore any originally suggested usage. Please consider using it to suggest anything that you would like to share with us all.
Please see later note added above which overrides anything suggested/recommended below.
It may be helpful if there was somewhere that subscribers who discover some issue with a particular job after downloading the data, could advise others. This would be up to each individual should they wish to do so upon discovering something amiss. Strictly for issues related to the downloaded data so as to keep the number of posts in this thread to a minimum.
You would need to check the box on this post if you do want be notified of replies to this topic, and thereby be informed of anything newly discovered.
The catch-22 is that you would need to actually access this post first, and right now you're completely unaware of its existence. Now if those with the privileges to do so think this may be a good idea, then they could create a catch-all post and suggest that everyone has a look. Only they have the power to do that kind of thing. Each syndicate where there is more than 1 person could have the same thing.
Anyway, I've just noticed that this pier had another funny turn. This affects the last 12 Sulphur subs for job (00)1064 part of the Sadr mosaic. Although the Fits header contains the correct coordinates, the area of sky captured in all those subs is out of alignment. I have seen this occasionally before on this pier. You would be made aware of this during alignment, but I already encountered the situation where WBPP decided to use such a frame for the master alignment! Could only ever happen to me.
Clear skies.
Please see later note added above which overrides anything suggested/recommended below.
It may be helpful if there was somewhere that subscribers who discover some issue with a particular job after downloading the data, could advise others. This would be up to each individual should they wish to do so upon discovering something amiss. Strictly for issues related to the downloaded data so as to keep the number of posts in this thread to a minimum.
You would need to check the box on this post if you do want be notified of replies to this topic, and thereby be informed of anything newly discovered.
The catch-22 is that you would need to actually access this post first, and right now you're completely unaware of its existence. Now if those with the privileges to do so think this may be a good idea, then they could create a catch-all post and suggest that everyone has a look. Only they have the power to do that kind of thing. Each syndicate where there is more than 1 person could have the same thing.
Anyway, I've just noticed that this pier had another funny turn. This affects the last 12 Sulphur subs for job (00)1064 part of the Sadr mosaic. Although the Fits header contains the correct coordinates, the area of sky captured in all those subs is out of alignment. I have seen this occasionally before on this pier. You would be made aware of this during alignment, but I already encountered the situation where WBPP decided to use such a frame for the master alignment! Could only ever happen to me.
Clear skies. This was set up initially to share issues with this pier but in the absence of a means to send a notification to all members, please ignore any originally suggested usage. Please consider using it to suggest anything that you would like to share with us all.
Please see later note added above which overrides anything suggested/recommended below.
It may be helpful if there was somewhere that subscribers who discover some issue with a particular job after downloading the data, could advise others. This would be up to each individual should they wish to do so upon discovering something amiss. Strictly for issues related to the downloaded data so as to keep the number of posts in this thread to a minimum.
You would need to check the box on this post if you do want be notified of replies to this topic, and thereby be informed of anything newly discovered.
The catch-22 is that you would need to actually access this post first, and right now you're completely unaware of its existence. Now if those with the privileges to do so think this may be a good idea, then they could create a catch-all post and suggest that everyone has a look. Only they have the power to do that kind of thing. Each syndicate where there is more than 1 person could have the same thing.
Anyway, I've just noticed that this pier had another funny turn. This affects the last 12 Sulphur subs for job (00)1064 part of the Sadr mosaic. Although the Fits header contains the correct coordinates, the area of sky captured in all those subs is out of alignment. I have seen this occasionally before on this pier. You would be made aware of this during alignment, but I already encountered the situation where WBPP decided to use such a frame for the master alignment! Could only ever happen to me.
Clear skies.
Ray
Roboscopes Guinea Pig
0
Undo
Votes
A 4 panel mosaic of the Sadr star region in Cygnus.
Masterminded by Richard and comprised of the datasets 1063,1064,1065 & 1066.
This unfortunately did not come without a few issues and unless you were able to follow update posts in real time it's likely to be a bit confusing. Data for 2 parts of the mosaic covered by jobs 1065 and 1066, somehow ended up in job 1065. Initial inspection of that job led to an incorrect conclusion that it was all for job 1066 and nothing for 1065. This resulted in job 1065 being resubmitted. (At the time of writing this has just started being collected) It was only later on closer inspection of all of the data within job 1065 that it was found to contain both 1066 and 1065, necessitating the moving of the incorrect files out of the dataset.
What we should end up with, assuming the current new resubmission of job 1065 is made available, are 5 data sets.
The data sets 1063,1064 and 1066 are all as they should be, but the original 1065 contains subs for both 1065 plus many for 1066. How this happened I don't know, but the instructions below will help you remove that data from 1065 and move it to where it should be in 1066. This will result in many more subs for the area covered by 1066 compared to the others. The next paragraph gives an update on the situation.
Since looking this morning, 28th August, at the job queue it appears that the resubmitted job for the 1065 data, initially thought to be missing, is now nearly complete. If and when we receive that it can be combined with the data we already have. This would offer the opportunity to use the 2 panels 1065 and 1066, which would then each have about double the data, as a smaller mosaic or maybe a crop of that mosaic. Just a suggestion.
Instructions on moving the data for 1066 out of the original 1065 now follow.
These are the (files/images/subs, frames) or whatever you want to call them, you need to move from the original submission 1065 into 1066 by filter.
Hydrogen:- Move all subs captured on 20210721 from 1065 into 1066. 20 in total.
Sulphur:- Move subs 20210729-005623 thru 20210731-012158 from 1065 into 1066. 40 in total
Oxygen:- Move subs 20210729-012325 thru 20210730-033212 from 1065 into 1066. 18 in total then,
finally move subs 20210731-013202 thru 20210731-024026 from 1065 into 1066. 12 in total
The oxygen ones need to done in 2 parts as a result of interleaving times in the 2 datasets.
You could always choose just to use the newer 1065 dataset instead and not use the older one and not do the above.
If you do have any questions then please, please put them in the Sadr 1,2,3,4 post. I or anyone can reply there and then I'll update this one if necessary with that information. I'd really like to keep everything in this one post. Thanks for your cooperation.
Update 31st August.
I'd recommend removing the last 12 subs from the Sulphur data in dataset 1064, as mentioned in the original post.
When tackling this particular mosaic using Pixinsight I'd highly recommend reading the extremely useful article by Richard in the Imaging Tips section titled, "Mosaic construction using Photometric Mosaic Script". Whilst not essential to follow everything, you'll likely end up with bad star shapes within the mosaic and not just the corners and edges. Only noticeable with a small amount of pixel peeping.
Cheers,
Ray
Masterminded by Richard and comprised of the datasets 1063,1064,1065 & 1066.
This unfortunately did not come without a few issues and unless you were able to follow update posts in real time it's likely to be a bit confusing. Data for 2 parts of the mosaic covered by jobs 1065 and 1066, somehow ended up in job 1065. Initial inspection of that job led to an incorrect conclusion that it was all for job 1066 and nothing for 1065. This resulted in job 1065 being resubmitted. (At the time of writing this has just started being collected) It was only later on closer inspection of all of the data within job 1065 that it was found to contain both 1066 and 1065, necessitating the moving of the incorrect files out of the dataset.
What we should end up with, assuming the current new resubmission of job 1065 is made available, are 5 data sets.
The data sets 1063,1064 and 1066 are all as they should be, but the original 1065 contains subs for both 1065 plus many for 1066. How this happened I don't know, but the instructions below will help you remove that data from 1065 and move it to where it should be in 1066. This will result in many more subs for the area covered by 1066 compared to the others. The next paragraph gives an update on the situation.
Since looking this morning, 28th August, at the job queue it appears that the resubmitted job for the 1065 data, initially thought to be missing, is now nearly complete. If and when we receive that it can be combined with the data we already have. This would offer the opportunity to use the 2 panels 1065 and 1066, which would then each have about double the data, as a smaller mosaic or maybe a crop of that mosaic. Just a suggestion.
Instructions on moving the data for 1066 out of the original 1065 now follow.
These are the (files/images/subs, frames) or whatever you want to call them, you need to move from the original submission 1065 into 1066 by filter.
Hydrogen:- Move all subs captured on 20210721 from 1065 into 1066. 20 in total.
Sulphur:- Move subs 20210729-005623 thru 20210731-012158 from 1065 into 1066. 40 in total
Oxygen:- Move subs 20210729-012325 thru 20210730-033212 from 1065 into 1066. 18 in total then,
finally move subs 20210731-013202 thru 20210731-024026 from 1065 into 1066. 12 in total
The oxygen ones need to done in 2 parts as a result of interleaving times in the 2 datasets.
You could always choose just to use the newer 1065 dataset instead and not use the older one and not do the above.
If you do have any questions then please, please put them in the Sadr 1,2,3,4 post. I or anyone can reply there and then I'll update this one if necessary with that information. I'd really like to keep everything in this one post. Thanks for your cooperation.
Update 31st August.
I'd recommend removing the last 12 subs from the Sulphur data in dataset 1064, as mentioned in the original post.
When tackling this particular mosaic using Pixinsight I'd highly recommend reading the extremely useful article by Richard in the Imaging Tips section titled, "Mosaic construction using Photometric Mosaic Script". Whilst not essential to follow everything, you'll likely end up with bad star shapes within the mosaic and not just the corners and edges. Only noticeable with a small amount of pixel peeping.
Cheers,
Ray
Ray
Roboscopes Guinea Pig
0
Undo
Votes
I'm having trouble trying to find a post where everyone I'm aware of in this syndicate has replied, and will receive a notification. Hence I'm hoping that by making a post here will notify everyone.
This discussion relates to a submission by Vikas last month to image Sh2-129 (the Flying bat) and the Squid (ou4), which itself is a faint oxygen rich object in the same fov. This submission was removed from the joblist and a decision on resubmission postponed. Alas it wasn't until today that I discussed this with Steve.
Some of the Syndicate will already have received data for this and therefore may not be acceptable to spending further time on it. I believe the results we received left us requiring a bit more oxygen data for the Squid, but not all of us may be interested. I'm aware that Vikas has no data, having joined the Syndicate after the data capture.
I consulted with a guru as to what the best solution and compromise might be and this is what the brummie guru suggested.
Submit a job for say 4 hours hydrogen and 10 hours oxygen.
There is no guarantee that this would result in the improvement, for those of us who have the data, to more clearly reveal the Squid within the brighter Flying bat. For Vikas this may not be satisfactory at all.
So what do we do? Any other compromise suggestions are welcome in the meantime.
I suggest we wait for replies from everyone first, so please reply asap.
Cheers,
Ray
This discussion relates to a submission by Vikas last month to image Sh2-129 (the Flying bat) and the Squid (ou4), which itself is a faint oxygen rich object in the same fov. This submission was removed from the joblist and a decision on resubmission postponed. Alas it wasn't until today that I discussed this with Steve.
Some of the Syndicate will already have received data for this and therefore may not be acceptable to spending further time on it. I believe the results we received left us requiring a bit more oxygen data for the Squid, but not all of us may be interested. I'm aware that Vikas has no data, having joined the Syndicate after the data capture.
I consulted with a guru as to what the best solution and compromise might be and this is what the brummie guru suggested.
Submit a job for say 4 hours hydrogen and 10 hours oxygen.
There is no guarantee that this would result in the improvement, for those of us who have the data, to more clearly reveal the Squid within the brighter Flying bat. For Vikas this may not be satisfactory at all.
So what do we do? Any other compromise suggestions are welcome in the meantime.
I suggest we wait for replies from everyone first, so please reply asap.
Cheers,
Ray
Ray
Roboscopes Guinea Pig
0
Undo
Votes
Hi Vikas,
Thanks for replying. You may change your mind if you're still interested after reading the following.
It's not ethical or really allowed to share data previously collected , but Steve has magnanimously agreed in this one instance to allow sharing. This does not set a precedent. The data previously collected, which would have to be as 2 calibrated and aligned filter stacks since roboscopes no longer has the original data, is all that would need sharing. I do have those but have no idea on how I'd be able to get them to you as of now. This would equally apply to Florent and Mark if they read this post.
This would allow us to submit a job just for more oxygen data, we already have about 13 hours!
Regards,
Ray
Thanks for replying. You may change your mind if you're still interested after reading the following.
It's not ethical or really allowed to share data previously collected , but Steve has magnanimously agreed in this one instance to allow sharing. This does not set a precedent. The data previously collected, which would have to be as 2 calibrated and aligned filter stacks since roboscopes no longer has the original data, is all that would need sharing. I do have those but have no idea on how I'd be able to get them to you as of now. This would equally apply to Florent and Mark if they read this post.
This would allow us to submit a job just for more oxygen data, we already have about 13 hours!
Regards,
Ray
Ray
Roboscopes Guinea Pig
Hi All,
I have the original raw data from our earlier attempt at SH2-129 and OU-4. We realised the squid was faint, but even though we got 155 x 300sec reasonable frames of O3 you still have to really squint to see it in the calibrated and stacked image.
Some of the best images I have seen involve insane amounts of integration time. This image used a total of 131 hours integration. An earlier version from the same imager used a mere 55 hours.
So we have 12 hours of O3. I would try and double that if we are serious and see where that gets us.
I have put the data in my cloud account and will send the link to any of you that would like this data. Just email me richard@miller-klein.com. I am doing it this way, rather than putting the link up here to keep it to syndicate members.
Be warned it is a 13.5GB file even after I have stripped out the obvious no-hope subs.
I could just send you the calibrated and stacked masters, but that would involve trusting my processing capabilities, which I don't recommend. Much better to start from scratch.
Old_eyes
I have the original raw data from our earlier attempt at SH2-129 and OU-4. We realised the squid was faint, but even though we got 155 x 300sec reasonable frames of O3 you still have to really squint to see it in the calibrated and stacked image.
Some of the best images I have seen involve insane amounts of integration time. This image used a total of 131 hours integration. An earlier version from the same imager used a mere 55 hours.
So we have 12 hours of O3. I would try and double that if we are serious and see where that gets us.
I have put the data in my cloud account and will send the link to any of you that would like this data. Just email me richard@miller-klein.com. I am doing it this way, rather than putting the link up here to keep it to syndicate members.
Be warned it is a 13.5GB file even after I have stripped out the obvious no-hope subs.
I could just send you the calibrated and stacked masters, but that would involve trusting my processing capabilities, which I don't recommend. Much better to start from scratch.
Old_eyes
0
Undo
Votes
Richard,
Thanks for doing that. I'd really recommend the stacks for anyone using Pixinsight. I'm sure we'd all end up with pretty much the same results if we use WBPP. Also I'm sure anyone would appreciate the time saved by not having to calibrate all those subs. If I hadn't already done it I know what I and my laptop would prefer.
Phil, the original job was 0024 so that should give you some idea how long ago it was. There was an additional one for more oxygen which I'm sure Richard knows, but you're equally unlikely to have.
Great cooperation on this syndicate on so many fronts, and I'm glad I'm in it.
Cheers
Ray
Thanks for doing that. I'd really recommend the stacks for anyone using Pixinsight. I'm sure we'd all end up with pretty much the same results if we use WBPP. Also I'm sure anyone would appreciate the time saved by not having to calibrate all those subs. If I hadn't already done it I know what I and my laptop would prefer.
Phil, the original job was 0024 so that should give you some idea how long ago it was. There was an additional one for more oxygen which I'm sure Richard knows, but you're equally unlikely to have.
Great cooperation on this syndicate on so many fronts, and I'm glad I'm in it.
Cheers
Ray
Ray
Roboscopes Guinea Pig
0
Undo
Votes
That's a lot of integration time in that linked image! I'd be more than happy if we could capture between 120 and 160 x 300s new subs, just in O3. Do we have any need for additional Ha data? Maybe by now others may have done an initial process, thanks to Richard, and are now be able to make a suggestion for what additional data we should go for.
Cheers,
Ray
Cheers,
Ray
Ray
Roboscopes Guinea Pig
To get an idea of the data, here are my stacked Ha and O3 images. Just a Masked Stretch applied, cropped to the key central area where the squid is, and exported as JPG.
Ha
O3
As you can see, the squid is visible in O3 providing you know where it is and have the eye of faith.
I think another 150 subs in O3 would help. Are we agreed?
Ha
O3
As you can see, the squid is visible in O3 providing you know where it is and have the eye of faith.
I think another 150 subs in O3 would help. Are we agreed?
0
Undo
Votes
I agree with Mark, that ought to be what someone submits, so no pressure Richard. 
Ray
Roboscopes Guinea Pig
0
Undo
Votes
Should we collect more OIII for spaghetti nebula? I just process the data and found at least 70-80 images of the OIII were impacted by the cloud so the signal is pretty weak.
Should we collect 100 x 300s more for the OIII similar to the flying bat?
Should we collect 100 x 300s more for the OIII similar to the flying bat?
- Page :
- 1
- 2
There are no replies made for this post yet.
Be one of the first to reply to this post!
Be one of the first to reply to this post!
Proud to use
Resources
Company Details:
Roboscopes
802 Kingsbury Road
Birmingham
B24 9PS
United Kingdom
