const
Active member
Ask me if you never get negative values in integrated images and I will upload some shots from my superdark site
So, my process is simple:
ImageIntegration sometimes rescales or truncates the output when the original range extends to the negative space. I guess, DrizzleIntegration is not as careful.
How is it even possible to get negative values when all inputs are strictly non-negative? What is the right workaround for master light, rescale or truncate?
So, my process is simple:
- WBPP calibrate only using darks, flats, and flat darks.
- StarAlignment.
- ImageIntegration with Noise weighting and Linear Fit or ESD rejection with default parameters. Discard the resulting image.
- DrizzleIntegration. Scale 1, Drop shrink 1, Enable CFA drizzle, all other defaults.
- STF AutoStretch resulting image — boom!
Code:PixInsight 1.8.8-5 - Critical Signal BacktraceReceived signal 11 (SIGSEGV) Module: /opt/PixInsight/bin/PixInsight(+0x16d1f41) [0x564cec18ef41] ================================================================================ 6: /lib64/libpthread.so.0(+0x13070) [0x7ffb706b0070] 5: void pi::RenderThreadBase::Render<pcl::FloatPixelTraits>(pcl::GenericImage<pcl::FloatPixelTraits> const*)(+0x215f [0x564ceb15feaf]) 4: pi::RenderThread<pcl::FloatPixelTraits, pcl::FloatPixelTraits>::run()(+0x53 [0x564ceb552f73]) 3: /opt/PixInsight/bin/lib/libQt5Core.so.5(+0xc75b2) [0x7ffb672ae5b2] 2: /lib64/libpthread.so.0(+0x7f77) [0x7ffb706a4f77] 1: /lib64/libc.so.6(clone+0x3f) [0x7ffb66433f8f](+0x3f [0x7ffb66433f8f]) ================================================================================ terminate called after throwing an instance of 'pcl::EUnixSegmentationViolation' Received signal 6 #0 0x7ffb6ade4fae base::debug::StackTrace::StackTrace() #1 0x7ffb6ade3e83 base::debug::(anonymous namespace)::StackDumpSignalHandler() #2 0x7ffb6ade4f16 base::debug::(anonymous namespace)::StackDumpSignalHandler() #3 0x7ffb706b0070 <unknown> #4 0x7ffb663726c1 gsignal #5 0x7ffb6635c53b abort #6 0x7ffb6670c87e <unknown> #7 0x7ffb66718486 <unknown> #8 0x7ffb667184f1 std::terminate() #9 0x7ffb672754a9 qTerminate() #10 0x7ffb67276ef2 _ZN14QThreadPrivate5startEPv.cold #11 0x7ffb706a4f77 start_thread #12 0x7ffb66433f8f clone r8: 0000000000000000 r9: 00007ffa777fdac0 r10: 0000000000000008 r11: 0000000000000246 r12: 00007ffad4005b90 r13: 00007ffd5afbb5ef r14: 00007ffa777fe700 r15: 00007ffa777fde80 di: 0000000000000002 si: 00007ffa777fdac0 bp: 0000564cec3a0140 bx: 00007ffa777fe700 dx: 0000000000000000 ax: 0000000000000000 cx: 00007ffb663726c1 sp: 00007ffa777fdac0 ip: 00007ffb663726c1 efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000004 trp: 000000000000000e msk: 0000000000000000 cr2: 0000564df787664e [end of stack trace] Calling _exit(1). Core file will not be generated.
ImageIntegration sometimes rescales or truncates the output when the original range extends to the negative space. I guess, DrizzleIntegration is not as careful.
How is it even possible to get negative values when all inputs are strictly non-negative? What is the right workaround for master light, rescale or truncate?