Тема: Обробка астрофото із Siril (Прочитано 8416 раз)

mpyat2

Hi Cyril,

I have strange problems while creating my (new) new login to your bug-tracking system (probably something wrong on my side, I will try from home later).

So I will describe two (minor) bugs here I've found so far:

1) Siril under Windows v 0.9.9: main menu: File->"Open..." dialog seems has no parent window: you can click on the still active main window and open other dialogs (including secondary Open dialog). "Save As" dialog works normally (it disables the main window as expected).

2) "File conversion" tab: while converting DSLR RAW files having "Demosaicing" box checked (unusual case, yet legal), AHD interpolation is used regardless of configured interpolation method (see screenshot)

lock042

Hello.

1 - MMMMMMhhh ok. I will take a look to that 1.

2 - This is not a bug. Here, in your example you are debayering a DSLR Raw image. So you need to go to the tab "DSLR RAW debayer" in the setting box. Indeed, these are two different things as DSLR RAW images are demosaiced by external library while Siril FITS are demosaiced by internal code.

Cheers,

mpyat2

Hi,

Well, really, the second one is not a bug! Sorry!

lock042

1 has been fixed: https://gitlab.com/lock042/Siril-0.9/commit/e5dac835edf46f5a528d9e3c455650c2754ea432

mpyat2

Hi Cyril,

I saw that there are plans to move Siril basic FITS format from unsigned integers to floats. Is it true?

I'm asking because now there are some problems with negative values which arise in the calibration process (due to noise). As I see, all of them are clipped by zeros in the resulting calibrated images. When we use DSLR roadmap without dark optimization, such clipping occurs in the final calibrated images only (which is also not good, because introduces some bias while performing photometry, for example); with optimization of darks, when we should use master dark calibrated with master-bias, such kind of zero-clipping arise in master-dark frames, which is even worse, I think.
What do you think about this?

Best regards,
Max

lock042

Hello.

Indeed it is true. We will working to make floats as Siril precision. However, it will take time as we know working hard on another difficult feature.
But, for now I don't really know how are handled negative value in FITS library. Indeed, it is not impossible that negatives values are also clipped. I think that PixInsight allows to apply a pedestal value to avoid this kind of Issue.

mpyat2

Hi, Cyril,

There is an apparently minor bug: while stacking with normalization, the log is displayed incorrectly (actual normalization is indeed done)

Best regards,
Max

lock042

Oh. I will take a look asap !!

Thanks.

lock042

Hello. Did you improve the translation ?

AYN

Hello,
Siril is a great and useful tool. Wish it could handle RAW files of some newer cameras, for example mine Fujifilm X-A3 (with buyer sensor) or earlier Fujifilm X-T10 (non-bayer sensor). When I try to load / create sequence of raw images from X-A3 camera for example, Siril generates :
Decoding Fujifilm X-A3 file (ISO=200, Exposure=1/680s)
17:00:32: Daylight multipliers: 1.000000, 1.000000, 1.000000
17:00:32: AHD interpolation...
17:00:32: Execution time: 547.21 ms.

- but doesn't generate anything... No error, no warnings, just silently moves on to the next raw image and then to the end of sequence... It would be great at least to show some warning if it cannot handle raw files of unknown format...

P.S. By the way - lastest libraw 0.19 can demosaic RAW files of all mentioned above cameras.

mpyat2

Цитата: lock042 від 05 Вересня 2018, 14:58:45

Hello. Did you improve the translation ?

Slightly. There were quite good weather so I spent time observing and made very little progress. However I will not give up.

mpyat2

Цитата: AYN від 05 Вересня 2018, 17:15:42

Hello,
Siril is a great and useful tool. Wish it could handle RAW files of some newer cameras, for example mine Fujifilm X-A3 (with buyer sensor) or earlier Fujifilm X-T10 (non-bayer sensor). When I try to load / create sequence of raw images from X-A3 camera for example, Siril generates :
Decoding Fujifilm X-A3 file (ISO=200, Exposure=1/680s)
17:00:32: Daylight multipliers: 1.000000, 1.000000, 1.000000
17:00:32: AHD interpolation...
17:00:32: Execution time: 547.21 ms.

- but doesn't generate anything... No error, no warnings, just silently moves on to the next raw image and then to the end of sequence... It would be great at least to show some warning if it cannot handle raw files of unknown format...

P.S. By the way - lastest libraw 0.19 can demosaic RAW files of all mentioned above cameras.

For Fujifilm X-A3 you could use iconvraw.exe from my https://sourceforge.net/projects/fits-command-line-utilities/ as temporarily solution.

AYN

Цитата: mpyat2 від 05 Вересня 2018, 17:49:14

For Fujifilm X-A3 you could use iconvraw.exe from my https://sourceforge.net/projects/fits-command-line-utilities/ as temporarily solution.

Yes, I know

Thanks. But I would prefer not to use external raw converters since Sirils itself can do the same internally for other cameras... )

lock042

Thank you.

Fuji Xtrans should be already readable with the 0.9.9 version.

lock042

mpyat2: good news for you

mpyat2

It’s fine! I will ckeck.
Yet the problem remains with negative values.
Do you plan to introduce something like “pedestal”?

lock042

Yes we could, but yet you can use the "offset" command in order to do the same.

mpyat2

Not the same: pedestal is hidden feature, offset adds real shift, so, for example, dark with offset removed losses negative values (caused by noise) and gets biased, which is important for fotometry.

lock042

Here is how PI is doing: https://pixinsight.com/forum/index.php?topic=2182.0

AYN

Цитата: lock042 від 05 Вересня 2018, 21:58:15

Thank you.

Fuji Xtrans should be already readable with the 0.9.9 version.

Yes, xtrans works perfectly for X-T10. Great. Thanks.

However conversion doesn't work for Fujifilm X-A3 (bayer sensor).

Sample output from command 'siril <test.RAF>' for X-T10:

MODE: closing sequence
log: Decoding Fujifilm X-T10 file (ISO=1600, Exposure=1/18.0 sec)
log: Bayer pattern: RBGBRGGGRGGBGGBGGRBRGRBGGGBGGRGGRGGB
log: Reading RAW: file RAW_FUJI_X-T10.RAF, 1 layer(s), 4934x3296 pixels
Loading image OK, now displaying
MODE: closing sequence

for X-A3:

MODE: closing sequence
FXA33151.RAF: Unexpected end of file
Error in libraw Input/output error
log: Opening FXA33151.RAF failed.
MODE: closing sequence

I also thinking that "bayer pattern" is not really correct naming for all types of raw files in output, probably more common like "CFA pattern" would be more close?

Новини:

Автор Тема: Обробка астрофото із Siril (Прочитано 8416 раз)