Request for Data Collaboration of Sh2-174

I’d probably be down for some collaboration. I haven’t shot this object before so could be interesting. I’m currently trying to finish up a few projects but could probably start devoting some time to it pretty soon. What are you looking for? Just calibrated and integrated masters?

I also see you did some time on SH2-188. I’ve been pondering doing that one as well so could probably do the same with that target.

Arun H · Oct 14, 2025, 03:13 PM

Rodd Dryfoos:
If anyone is interested in sharing data to create a very deep image of Sh2-174? I collected 30 hours (22.5 Ha and 7.5 OIII). The image is attached here. Some of the Ha emissions in the upper right look interesting, but are very faint. It would be interesting to see what features present themselves with many hours of data.

It would be interesting to try this with any data, so if you have a preference, and I have posted an image that may be appropriate, please let me know. Most of my data is saved as linear masters. Space being limited, I don’t keep individual subs. But I have alot of success combining stacks from different scopes. So I think this will not be a limitation.

WXmitvCHGr69_16536x0_PPEMZ4TF.jpg

Rodd - see this image here. 

https://astrob.in/9vmi26/


If it is of interest to you, the data can be combined to see that can be made of it and I am happy to share the calibrated files.


My request here would be that you share your linear calibrated files with me too and maybe we could make two versions of a combined image.

I think our data would work well together. Similar pixel scale, similar FOV. We will lose some around the sides, I’m sure, but that’s inevitable. My suggestion is we set up a repository where anyone (or any authorized person) can upload their data and use whichever data they want in the repository to make an image. Certain data will be work better with certain other data based on FOV, pixel scale, filters used, etc. Unfortunately, I don’t know how to do this. I’m wondering if Astrobin has a similar capability.

Rodd Dryfoos · Oct 15, 2025, 11:01 AM

Astrobin has a raw data capability, but i’m not sure if we can download someone from else’s page

Uncompressed data source files, which I suppose you refer to, are private to the user who uploaded them.

Rodd Dryfoos · Oct 14, 2025 at 01:51 PM

If anyone is interested in sharing data to create a very deep image of Sh2-174? I collected 30 hours (22.5 Ha and 7.5 OIII). The image is attached here. Some of the Ha emissions in the upper right look interesting, but are very faint. It would be interesting to see what features present themselves with many hours of data.

It would be interesting to try this with any data, so if you have a preference, and I have posted an image that may be appropriate, please let me know. Most of my data is saved as linear masters. Space being limited, I don’t keep individual subs. But I have alot of success combining stacks from different scopes. So I think this will not be a limitation.

WXmitvCHGr69_16536x0_PPEMZ4TF.jpg

Hi Rodd,

Happy to share my data — let me know how you’d like to proceed.

I imaged Sh2-174 back in 2022: https://app.astrobin.com/i/b90woy/

For what it’s worth, another collective published some tutorial about their approach and lessons learned from collaborating https://deepskycollective.com/tutorials

/Ralf

Hi Rodd,

Assuming you aim to collect approximately 1’000 frames, the total storage requirement would be at least 100 GB (asssuming calibrated, uncompressed mono frames in XISF format from a QHY268M or ASI2600MM).
For OSC data, the file size would increase by a factor of three, as all three color channels are stored.

Storage requirements are significant, so it's important to allocate sufficient space using a cloud service (e.g., Dropbox, OneDrive, iDrive, etc.) or alternatively set-up your own FTP server

Before going futther, I think you should define the process, a clear folder structure and file naming convention to facilitate data processing and collaboration.

Once ready, you give participants access to the storage and inform them about the guidelines for contributing data.

You probably want to collect already calibrated data in XISF format (asssuming you use PixInsight), e.g. each participant would be responsible to calibrate and cull their own data before submitting.

For the actual processing, you will need a multiple of the above storage capacity available locally,

I suggest that you read the tutorial at https://deepskycollective.com/tutorials/preprocessing to get you started. I believe the people behind this project are also on AstroBin and might have additional insights?

/Ralf

FlapAstro · Oct 16, 2025, 02:57 PM

Hi Rodd,

Assuming you aim to collect approximately 1’000 frames, the total storage requirement would be at least 100 GB (asssuming calibrated, uncompressed mono frames in XISF format from a QHY268M or ASI2600MM).
For OSC data, the file size would increase by a factor of three, as all three color channels are stored.

Storage requirements are significant, so it's important to allocate sufficient space using a cloud service (e.g., Dropbox, OneDrive, iDrive, etc.) or alternatively set-up your own FTP server

Before going futther, I think you should define the process, a clear folder structure and file naming convention to facilitate data processing and collaboration.

Once ready, you give participants access to the storage and inform them about the guidelines for contributing data.

You probably want to collect already calibrated data in XISF format (asssuming you use PixInsight), e.g. each participant would be responsible to calibrate and cull their own data before submitting.

For the actual processing, you will need a multiple of the above storage capacity available locally,

I suggest that you read the tutorial at https://deepskycollective.com/tutorials/preprocessing to get you started. I believe the people behind this project are also on AstroBin and might have additional insights?

/Ralf

Thanks Ralf. Actually—I’m thinking something much easier—just the linear masters. Folks can calibrate and integrate then post the master stacks. Storage for that is limited to a few gigs. That way, we all can download the stacks and process them on our systems as we would do any image.