Jump to content

JCIdaho

Members
  • Posts

    36
  • Joined

  • Last visited

Posts posted by JCIdaho

  1. Hi @globular - Thanks! I have to say, it's extremely confusing. Looking at what you posted, I would agree the backfocus from the end of the flattener to the sensor should be 65.7mm.

    But, have a read of this: https://www.cloudynights.com/topic/833579-william-optics-flat-68iii/.

    That convinces me the backfocus should be 65.7 - 10.7mm = 55mm.

    If this is indeed the case, then their website/specification is v poor and confusing?

    As for what you say "And I suspect that all this is optimised for the flattener directly connected to the telescope thread..."

    Agree - this is my hunch too. I'm tempted to test it anyway, and gamble the cost of the custom adapter if it doesn't work. The adapter may one day (?) come in handy if I don't use!

     

     

  2. Hi, I'm buying a new rig to send out to a remote site.

    I'd really appreciate any second pair of eyes on the following image train. The backfocus for the 68III should be 55mm, I hope this will be close enough..

      Aperture In Aperture Out Length
    WOFTL120   M92F  
    68III Field Flattener M92M M48M 17.5
    M48F to M68M M48F M68M 1.4
    Pegasus Falcon Rotator v2 M68F M68F 15.5
    M48M to M68M M68M M48M 1.4
    M54M-M48F-2 M48F M54M 2
    Zwo Filter Wheel M54F M48 20
    ZWO Tilt Plate M48   5
    ZWO asi2600mm     12.5
    Total     57.8

     

    thanks!

  3. Apologies for this @scotty38. Please see the below two images I originally meant to post.

    One is a sub after calibration:

    2024-03-04_04-24-27_R_-10.00_60.00s_0004_c.thumb.jpg.1a987c718697877d3a6179d76f00d257.jpg

    The other is the same sub, after calibration + registration.

    I've never seen this kind of weird lattice pattern before.

    As mentioned, this sub is the R. All the post registration subs have this problem. The other L/G/B subs are absolutely fine. The R flats look OK, so I'm just puzzled.

    2024-03-04_04-24-27_R_-10.00_60.00s_0004_c_r.thumb.jpg.dd483e69e625518e34e95b81806b55af.jpg

    thanks.

  4. Hi,

    (edited, - please see my next comment in this thread for a more accurate description of my issue)

    Please, any idea why this registration would result in the attached?

    During calibration it checks out OK - also attached.

    This is for all my R images - the L/G/B came out just fine, with the same bias frames etc.

    Thanks!

     

     

     

     

     

    2024-03-04_04-26-01_R_-10.00_60.00s_0005_c_r.jpg

    2024-03-04_04-26-01_R_-10.00_60.00s_0005_c.jpg

  5. On 15/01/2023 at 22:29, AstroGS said:

    Hi Gordon,

    It is the opposite I am afraid - I did widen the BB Planet's adaptor circumference by almost 1mm. I did not want to alter the PE200 as I will be using it with other tripods when I am in the field.

     

    Excuse me - how did you widen the adaptor by 1mm? Filing?

  6. Hi All,

    Looking at Trevor's latest video on YouTube, I'm quite taken with the Starfield Tri Pier. I've never considered a portable Tri Pier, but I'm considering now because a) I think I'd getting better guiding for my AM5 than the carbon fibre mount, b) thinking of getting a bigger refractor than my SM90, and the extra vertical clearance would help, c) more vertical clearance helps generally to access more sky, d) it just looks very cool, and I want one.

    There doesn't seem to me, to be much in the way of reviews for Tri Piers, probably because despite my reasons above, they aren't killer reasons? Has anyone had recent experience with a portable model, like this Starfield one, or perhaps the iOptron portable Tri Pier?

    I'm based in the UK, and so getting the Starfield one in Trevor's video could be tricky. I note that Altair Astro, that look a lot like the Starfield one, but they're out of stock.

    Any thoughts / recommendations welcome!

     

     

  7. Hi All,

    Appreciate some help. I messed up the rotation of the image train between consecutive nights, by a whopping 90 degrees difference! You can see below that I have 5 different exposures here for L: 60, 30, 15, 8, 4 seconds.

    On the first night I took the 15 seconds - the top right image - and you can see how registration has rotated it, but I've lost a substantial chunk in the process (the black areas).

     This is my first attempt at HDRComposition. If I blindly run HDRComposition against the five images, PI gives an error, which is fair enough: "Error: Inconsistent HDR composition detected (bad linear fit, channel 0)".

    Any ideas here? For completeness sake, the 30 exposure was completed over both nights, and you can see an imperfect blending of the two framings, in the middle left image, happening during registration.

    Is there a tool, to potentially stitch together two of the images, so I use the foreground of one, on top of the other, to allow HDRComposition to then work?

    I'd appreciate any advice on a route to take!

    Thanks.

     

    hdr.thumb.png.480fb036ced4c4d4b10245ac94b98647.png

  8. Hi All,

    This is my third go at M45. I'm going a bit blind looking at it! I'd really appreciate any feedback. My PixInsight process:

    R G B -> DBE, BX, LinearFit, ChannelCombination, BackgroundNeutralisation, HistogramTransformation

    L -> DBE, BX, HistogramTransformation

    LRGBCombination

    EZ Denoise

    HistogramTransformation

    RangeSelection Mask, then CurvesTransformation, increase saturation, make the background darker. More Curves work to try and make the blue pop out.

    XISF is here if anyone fancies poking about: https://drive.google.com/drive/folders/1an-M2oCxnTdO1diHoSP71UT143wgRG7K?usp=share_link

    thank you.

    m45-2.thumb.jpg.e935ca758a1cb6fdcb381abe162384ad.jpg

     

     

     

    • Like 4
  9. Hi,

    I look some data on M45 - there is some light pollution, which has caused some gradients and vignetting. It's a shame, as the image has the potential to look good I feel. I am new to LRGB processing, using an asi2600mm-pro camera. I'm using PixInsight.

    lrgb.thumb.jpg.400d0a4217232c012bf209c9596bc320.jpg

    I've tried running ABE (automatic background extractor) loads on the sub images, but when I combine RGB, I get the corners full of light, which makes creating a subsequent mask using RangeSelection difficult. Any tips would be appreciated. I can't seem to effectively kill these gradients! Is my data just too light polluted?

    lrgb.thumb.png.f85cda2dbbc3e8b2c79212e5cdb16d79.png

     

    The stacked-data for the LRGB images are here: https://drive.google.com/drive/folders/1d_W0KYxmWyDV_ONhkSR8elmxMXph-Q2B?usp=sharing.

    thanks.

     

     

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.