Forum Replies Created

Viewing 15 posts - 676 through 690 (of 1,281 total)
  • Author
    Posts
  • in reply to: Komeet C/2015 v2 Johnson #14759
    KeesScherer
    Participant

    C/2015 v2 Johnson op 1 mei 2017 23:03-23:13 UTC. 1 x 600 sec (QHY16200 op -20 C met IDAS LP2/ Esprit 100 f5.5) Nog steeds niet veel staart.

    KeesScherer
    Participant

    Hebbes! Het is T Cephei, een Mira variable met een periode van 388 dagen. Magnitude variabel tussen 5.2 en 11.3.

    KeesScherer
    Participant

    Why can’t we test this quickly and why won’t you let me help you?

    Because you don’t need to, i know what the problem is. My point is that the program has a built in indication next to the lights “B”, “F” but that indication has no meaning when you load all masters and lights. Furthermore there is no check done by APP for this so it just starts to stack. There needs to be a diagnostics step  that tells the user what is wrong at this point. And there needs to be a short, clear workflow with just the steps for calibration of DSLR images with flats taken at a different iso setting.

    A suggestion from me that will save you a lot of headaches in the future is to (And this is as we say in the Netherlands “Cursing in Church”) Add the following checkmark/option: “Calibrate flats with same (ISO/Gain) bias as Lights”

    KeesScherer
    Participant

    I will wait for the manual.

    KeesScherer
    Participant

    All individual flats need to be bias calibrated when you create the masterflat. So all flats need to have a b in the frame column before you create the masterflat. I’ll be happy to demonstrate it if it’s needed? Mabula

    No, you don’t need to do that Mabula, i will just wait for the manual before i will use APP for DSLR images. At This point in time APP just swallows everything i throw at it and stacks without any warning or guideline.

    KeesScherer
    Participant

    And here you can see that 3 lightframes have “B” and “F”, indicating flat calibration should have been done, but it isn’t……

    KeesScherer
    Participant

    I still have a problem. I load the masterbias iso200, the masterbias iso1600, the masterflat iso200 and the bad pixel map. Then i load lightframes iso1600, go to 6) integrate, leave everything at default and press “stack”. The result is a stack where the flat calibration is not done. (PS: Where is that manual?)

    The screenprint shows: top: Masterbias 200iso, Masterbias 1600 iso. left: masterflat iso200, right: resulting stack. (This was using a clip in-L  filter)

    KeesScherer
    Participant

    What would need to be “overridden” in your opinion?

    Nothing apparently, i forgot that i need to add iso200 Bias frames in addition to the iso1600 bias frames…… (A warning would help though as maybe i am not the only user who forgets about this)

    KeesScherer
    Participant

    Now back to the practical side, i have many objects imaged with the Canon 6Da in my archive and want to combine those RGB’s with new Luminance data. So i have years of iso1600 RGB data with corresponding iso200 flat frames. But there is no way that i can (re)stack this data with APP because the flat calibration is not done for these datasets. So i have to do the (re)stacking in Pixinsight if there is no “override” option for this.

    in reply to: Interpretation of Rejection maps #14621
    KeesScherer
    Participant

    Regarding the statistics and rejection of them: The outlier rejection works a little bit differently.

    Yes of course, but i will not do the calculation for the 65 frame stack by hand. The statistics for all the frames do not differ much from this “back of the envelope calculation”. The APP statistics for this master dark show a standard deviation of 125, close to the 112 that you see in one frame. (yes, that is sdev for all pixels in one frame versus one pixel in all frames so not correct either….)

    FITS HDUs: 1
    HDU1 – SIMPLE  =                    T / Java FITS: Sat Apr 29 11:01:14 BST 2017
    HDU1 – BITPIX  =                   16 / bits per data value
    HDU1 – NAXIS   =                    2 / number of axes
    HDU1 – NAXIS1  =                 4520 / size of the n’th axis
    HDU1 – NAXIS2  =                 3616 / size of the n’th axis
    HDU1 – EXTEND  =                    T / Extensions are permitted
    HDU1 – BSCALE  =                  1.0 / scaling to 16bit
    HDU1 – BZERO   =              32768.0 / offset data range to that of unsigned short
    HDU1 – DATE    = ‘2017-04-29T10:08:46’ / creation date of master dark
    HDU1 – SOFTWARE= ‘  Astro Pixel Processor by  Aries Productions’ / software
    HDU1 – CALFRAME= ‘master dark’        / master dark frame
    HDU1 – INSTRUME= ‘QHYCCD-Cameras-Capture’ / instrument name
    HDU1 – CFAIMAGE= ‘no      ‘           / Color Filter Array pattern
    HDU1 – GAIN    =                  1.0 / gain or ISO depending on instrument
    HDU1 – EXPTIME =                600.0 / exposure time (s)
    HDU1 – MEAN    = ‘ 7.79E+02’          / mean of channel
    HDU1 – MED     = ‘ 7.75E+02’          / median of channel
    HDU1 – SIGMA   = ‘ 1.25E+02’          / standard deviation of channel
    HDU1 – NOISE   = ‘ 2.50E+00’          / MRS gaussian noise estimate of channel

     

    in reply to: Interpretation of Rejection maps #14615
    KeesScherer
    Participant

    And some statistics, the cosmic ray has 1758 ADU, average=828 and sdev=112, so 828+3×112=1164. The 1758 gets rejected alright……

    in reply to: Interpretation of Rejection maps #14613
    KeesScherer
    Participant

    No problem! Just some examples:

    in reply to: Interpretation of Rejection maps #14610
    KeesScherer
    Participant

    Mabula, what am i looking at here, a master dark rejection map made from 65×600 seconds -20C darks. Cosmic ray hits?

    in reply to: Scopedome project Knight Observatory. #14605
    KeesScherer
    Participant

     There is very dangerous bug.

    De Scopedome heeft de rare gewoonte om aan het eind van de sessie eerst keurig naar “park” te gaan, om dan weer even terug te draaien naar de laatste positie en tenslotte weer naar “park”. Niet erg, maar onnodig. Toen ik naar de website van Scopedome ging om te kijken of andere gebruikers daar ook last van hebben trof ik deze hele merkwaardige melding:

    “If you have version 5.1.35 please uninstall it.
    There is very dangerous bug.”

    Ik heb het afgelopen half jaar versie 5.1.35 gebruikt…… Dus gelijk versie 5.1.36 geinstalleerd. En een email naar de customer service van Scopedome om te vragen waarom ze hun klanten niet aktief benaderd hebben hierover en wat nou dat “Dangerous” precies inhield. De Email correspondentie gaat vervolgens in “Pengels” (Scopedome is Pools). De meest uitgebreide toelichting die ik uiteindelijk kreeg: “This is bug connected with rotation limits.” Geen antwoord op mogelijke schade aan mens en machine. Ook tegen beter weten in gevraagd naar de oorzaak van de dome beweging aan het eind van een sessie, Scopedome wil dan teamviewer toegang tot mijn PC, die krijgt niemand en dus alle screenprints opgestuurd en alle logfiles waar ze om vroegen. Antwoord: ” I do not know, I can help you only via TeamViewer service session.” En dat had je mij ook van tevoren kunnen vertellen. Ik heb Scopedome geinformeerd dat ik nu via verschillende fora ga informeren of er andere Scopedomegebruikers zijn met dezelfde ervaring. Scopedome vond dat prima, zolang ik hun antwoorden maar erbij zou vermelden (Ha!).

    Het probleem zit niet in Sequence generator Pro want die geeft maar 1 keer opdracht tot parkeren aan de dome:

    04-27-17 13:46:22.912][DEBUG] [Sequence Thread] Checking RunEndOfSequenceEquipmentOptions, force = True
    [04-27-17 13:46:22.912][DEBUG] [Sequence Thread] In RunEndOfSequenceEquipmentOptions
    [04-27-17 13:46:54.546][DEBUG] [Sequence Thread] Parking telescope…
    [04-27-17 13:46:54.550][DEBUG] [Sequence Thread] ASCOM Telescope: Park message received.
    [04-27-17 13:46:54.550][DEBUG] [Sequence Thread] ASCOM Telescope: closing observatory shutter…
    [04-27-17 13:46:54.552][DEBUG] [Sequence Thread] Dome: Closing Shutter
    [04-27-17 13:47:35.927][DEBUG] [Main Thread] PopulateDataModel:  Transferring view to the data model…
    [04-27-17 13:47:35.931][DEBUG] [MF Update Thread] Performing serialize…
    [04-27-17 13:48:05.010][DEBUG] [Sequence Thread] ASCOM Telescope: parking observatory…
    [04-27-17 13:48:22.840][DEBUG] [Sequence Thread] ASCOM Telescope: Sending park…
    [04-27-17 13:48:35.016][DEBUG] [Sequence Thread] ASCOM Telescope: Parked
    [04-27-17 13:48:35.023][DEBUG] [Main Thread] Aborting sequence timer thread…
    [04-27-17 13:48:35.023][DEBUG] [Main Thread] Sending sequence end notification…
    [04-27-17 13:48:35.023][DEBUG] [Main Thread] Resetting UI elements…
    [04-27-17 13:48:35.023][DEBUG] [Main Thread] Checking if sequence has work left…
    [04-27-17 13:48:35.023][DEBUG] [Main Thread] No work left…

    in reply to: NGC 7023, 2017-04 Frankrijk – Grandpre #14602
    KeesScherer
    Participant

    Ik las dat de SQM waarden rond en boven de 22 waren?  Waarmee heb je de bewerkingen gedaan?

Viewing 15 posts - 676 through 690 (of 1,281 total)
Scroll to Top