Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.


  • Content Count

  • Joined

  • Last visited

Community Reputation

188 Excellent

1 Follower

About groberts

  • Rank
    Proto Star

Profile Information

  • Gender
  • Location
    Surrey, UK
  1. Thanks Mark, that makes perfect sense but was not what various tutorials seemed to say. After something of an uphill battle I feel near the finishing line (at least for this stage) and will try again tomorrow. Graham
  2. I've been battling to learn pre-processing for over a week now but have at last Calibrated, Corrected, Weighted etc subs for each LRGBHa wavelength, as instructed in the Light Vortex (LV) tutorial + all saved together in a single folder. Whilst the LV tutorial is generally excellent here and in other sources I'm unable to fathom out how to handle the subs in Image Integration - I get how to process x1 wavelength but not all five as in this case. Based on my experience with DSS, at this point I would expect to stack each wavelength separately i.e. load L subs into Image integration + Apply Global / run etc to produce a stacked L image, then move on to the next wavelength and do the same again. However, various sources seem to suggest I load all the subs (LRGBHa) and run them all together. Contrary to my intuition I have actually done this and I did prodcue a result but I'm baffled as to how to get form here to five stacked LRGBHa images or as I suspect, should I process each wavelenght one by one? Graham
  3. Great + thanks again - so far so good! The Registration worked fine but (as advised by Light Vortex) the next Local Normalisation step is unclear. Are the files used in this process, including the reference file, the original calibrated subs or those just generated by the Star Alignment process?
  4. Thanks, I think I'm having a 'senior moment' but it was not clear in either the otherwise excellent Light Vortex or Warren Keller + from DSS that's the route I would expect.
  5. Thank Hughsie, it certainly makes sense. Just to be clear - if I do this then obviously all the subs (LRGB) end up back where they were filed but now aligned? Presumably, if I wanted to preserve the subs as they were for some reason, I could set a new output directory and the said now aligned subs will instead go there for subsequent stacking? Graham
  6. Thanks but I'm still confused. I currently have LRGB subs calibrated, corrected and weighted in PI. In the next step, Star Alignment, do I either: (A) Put all the aforesaid LRGB subs into Star Alignment + choose one of the best subs as a reference and run? or (B) Put only each separate set of wavelength subs e.g. Red and then run + then move onto to the next wavelength and do the same again? Logically + experience with DSS suggests that all the subs are processed in Star Alignment with reference to a 'best sub', whichever wavelength that might be i.e. Case A?
  7. As a beginner with PI I'm working my way through the excellent Light Vortex tutorials + with reference to Warren Keller's book and have reached the Star Alignment section i.e. all subs have so far been calibrated, corrected etc. processed only with reference to others of the same wavelength L-R-G-B. In order to enforce what I'm reading I've been processing my own LRGB data I already have, which up until now has been wavelength by wavelength (see above). Now I'm at the alignment etc. stages but it's not clear to me where I start to process the subs together to ensure they are all aligned + registerted for subsequent integration; hitherto my experience is with Deep Sky Stacker so my preconceptions of how PI might deal with these stages is somewhat biased. So, assuming there are parallels at all - at what point herein do I start to process all the subs together, except of course for stacking itself? Thanks
  8. Excellent that's very helpful. I had of course tried Google but, as is often the case, came across a number of conflicting views. Don't understand what's happening with the driver scaling or why but happy to go with that. Many thanks David
  9. I'm slowly working through using PI for the first time and have arrived at the SubFrameSelector process.I have a late-2016 ZWO1600MM-Cool and just want to check the correct resolution input for this camera, which I believe is 12-bits. Please can someone confirm this or otherwise?Thanks
  10. I obviously did this with my current Lodestar x2 but that was three years ago and I'll obvioulsy need to do some revision before adding the new camera. Other than just getting the second camera to work, my main concern is to ensure I don't confuse the two cameras and ideally I'd therefore like to be able to name the new one differently. Thanks Wim. Graham
  11. Thanks Wim, this is what I fear. What do you exactly mean by two profiles + how would I do that?
  12. Thanks Wim, no only one at a time, just on different interchangeble rigs depending on conditions and targets. In PHD2 there's a dropdown 'forked' menu in the set-up connect section, which allows the addition of more than one camera or more of the same. I just don't understand how you then differentiate between each so as not to get them mixed up. Fortunately they will auotmatically create and store separate calibration files however. I'm also wondering if they'll use the same driver that's already installed. I suspect the only way to find out is to do it! Graham
  13. Many thanks Adam but no. See this separate thread I subsequently started as a result of this issue and have now purchased a Baader Varilock extender - see this thread for more info:
  14. I've just acquired a second Lodestar x2 guide camera for use with another rig and a different guidescope but operated from the same computer / PHD2 installation (not at the same time!). I can see in the manual that a second camera of the same type can be named via the "fork" button but wanted to check a few thoughts before I start to add my new camera: 1. As this is an identical camera can it be specifically named e.g. Lodestar-A or -B so as to clearly differentiate the two cameras thereafter? 2. Is it still possible to use the Connect All function using the two different set-ups + how? 3. Having installed the second camera, will each camera establish and thereafter use and identify with its own calibration files depending on which one is selected from the menu? 4. Anything else I need to be aware of / think about? Thanks, Graham
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.