- Welcome to Code Obsession Forum.
Code Obsession Forum
https://codeobsession.com
Recent posts
#31
Announcements / Observatory 2.1
Last post by Sander Berents - September 05, 2024, 01:40:47 AM #32
Announcements / Farewell Observatory 1
Last post by Sander Berents - September 05, 2024, 01:38:26 AM #33
General Discussion / Re: QL FITS etc not working
Last post by Tailspin45 - July 25, 2024, 03:35:58 PMJust loaded 105.8Gb in two folder, 8315 images in 3233.8 seconds. So it definitely solved the problem (avoided the glitch).
Set CPU Core allocation midway and it seems to be loading a new batch of folders, this time over 300Gb. However, it popped up a window with a progress bar but it disappeared so fast I couldn't get a screen grab. Activity shows it is working, though.
No crash reports for any Import attempt. Apparently when it hangs and I cancel the process it just politely quits.
And yes, another "duh-o" event. Of course the Import is a background event. And of course you can't create a background process for a background process.
I have a vague recollection, though, that a UNIX daemon can fork a child and grandchild...but those neurons last fired maybe a half century ago so I'm not sure it's even relevant.
Set CPU Core allocation midway and it seems to be loading a new batch of folders, this time over 300Gb. However, it popped up a window with a progress bar but it disappeared so fast I couldn't get a screen grab. Activity shows it is working, though.
No crash reports for any Import attempt. Apparently when it hangs and I cancel the process it just politely quits.
And yes, another "duh-o" event. Of course the Import is a background event. And of course you can't create a background process for a background process.
I have a vague recollection, though, that a UNIX daemon can fork a child and grandchild...but those neurons last fired maybe a half century ago so I'm not sure it's even relevant.
#34
General Discussion / Re: QL FITS etc not working
Last post by Sander Berents - July 25, 2024, 01:43:46 PMGreat! Please email a crash report for that 65 GB folder when using the default core allocation setting.
Import is already a background task. Observatory needs this information, and a background task of a background task is a bit too much.
Import is already a background task. Observatory needs this information, and a background task of a background task is a bit too much.
#35
General Discussion / Re: QL FITS etc not working
Last post by Tailspin45 - July 25, 2024, 12:15:12 PMQuote from: Sander Berents on July 25, 2024, 11:31:24 AMWhat dimensions and size are your images usually, and what format
I have five cameras that capture only FITS files
ASI462MC 2.1Mb 1920x1080
ASI533MC 9.05Mb 3008x3008
ASI294MC 11.7Mb 4144x2822
ASI678MC 8.29Mb 3840x2160
ASI120MM 1.2Mb 1280x 960
QuoteWhen you import, Observatory doesn't just create a thumbnail and add it to the library. It also computes image statistics, the average HFD of stars, tags plate solved images, etc. For large images, that just takes time.
Do that in the background after import is complete?
QuotePlease try to import the 65 GB folder with the core allocation set to its minimum value. There used to be a bug that could result in a crash when importing, and I found its cause after introducing the core allocation setting. Maybe you are hitting another concurrency bug.
That appears to be the case. With core set to minimum value the 63.15Gb folder with 1015 files loaded in 989.9 seconds
#36
General Discussion / Re: QL FITS etc not working
Last post by Sander Berents - July 25, 2024, 11:31:24 AMGood to hear that the Quick Look extension works now. But it's weird because Observatory doesn't need full disk access, and the Quick Look extension runs in its own sandbox. I have that turned off and it works fine for me.
The selection beachball I have resolved already for the next update. It was caused by excessive UI updates for things that weren't even displayed.
I have tested Observatory with folders larger than 65 GB, so the size is not the cause of the crash. What dimensions and size are your images usually, and what format? When you import, Observatory doesn't just create a thumbnail and add it to the library. It also computes image statistics, the average HFD of stars, tags plate solved images, etc. For large images, that just takes time.
Please try to import the 65 GB folder with the core allocation set to its minimum value. There used to be a bug that could result in a crash when importing, and I found its cause after introducing the core allocation setting. Maybe you are hitting another concurrency bug.
The selection beachball I have resolved already for the next update. It was caused by excessive UI updates for things that weren't even displayed.
I have tested Observatory with folders larger than 65 GB, so the size is not the cause of the crash. What dimensions and size are your images usually, and what format? When you import, Observatory doesn't just create a thumbnail and add it to the library. It also computes image statistics, the average HFD of stars, tags plate solved images, etc. For large images, that just takes time.
Please try to import the 65 GB folder with the core allocation set to its minimum value. There used to be a bug that could result in a crash when importing, and I found its cause after introducing the core allocation setting. Maybe you are hitting another concurrency bug.
#37
General Discussion / Re: QL FITS etc not working
Last post by Tailspin45 - July 25, 2024, 10:24:49 AMOnly one copy of Observatory. I also removed backup and clone copies.
No QL crash reports cataloged in Console.
Just updated a different program and had to go to Settings | Privacy & Security to give it full disk access and discovered Observatory was listed there but turned off. Enable it and everything seems to be working right! QL works and selecting subs from list causes no hiccoughs.
However, I still have that problem that the program refuses to load some folders. Interestingly, when I loaded sub-folders one-by-one, they loaded fine (and quickly).
I suspected, and further testing confirms, it's a size issue. It immediately quits importing a 65Gb folder full of lights, calibration files, and PixInsight by-product files such as Registered, Aligned, etc. But it happily loaded a 2.7Gb folder with 146 files in 93 seconds. Still waaaay to slow, but at least it loaded.
No QL crash reports cataloged in Console.
Just updated a different program and had to go to Settings | Privacy & Security to give it full disk access and discovered Observatory was listed there but turned off. Enable it and everything seems to be working right! QL works and selecting subs from list causes no hiccoughs.
However, I still have that problem that the program refuses to load some folders. Interestingly, when I loaded sub-folders one-by-one, they loaded fine (and quickly).
I suspected, and further testing confirms, it's a size issue. It immediately quits importing a 65Gb folder full of lights, calibration files, and PixInsight by-product files such as Registered, Aligned, etc. But it happily loaded a 2.7Gb folder with 146 files in 93 seconds. Still waaaay to slow, but at least it loaded.
#38
General Discussion / Re: QL FITS etc not working
Last post by Sander Berents - July 25, 2024, 03:54:04 AMBack to the original topic: Can you check your system if it has multiple copies of Observatory? The Quick Look extension can fail if the system loads it from a different copy than what you are using. If you have old copies of Observatory, make sure to compress them so the system doesn't recognize them as applications.
Please also check /Applications/Utilities/Console for Quick Look crash reports or other Quick Look related errors when viewing FITS, XISF or SBIG images.
Please also check /Applications/Utilities/Console for Quick Look crash reports or other Quick Look related errors when viewing FITS, XISF or SBIG images.
#39
General Discussion / Re: QL FITS etc not working
Last post by Tailspin45 - July 24, 2024, 11:51:27 AMQuote from: Sander Berents on July 24, 2024, 11:26:05 AMIf the exposure date/time is displayed correctly in the inspector, then you are probably sorting by import date/time, not exposure date/time. See the sort dropdown.
Well, duh. I completely forgot about that. Per usual, you thought of everything. I shoulda known. Thanks!
#40
General Discussion / Re: QL FITS etc not working
Last post by Sander Berents - July 24, 2024, 11:26:05 AMI did a quick selection test with a large number of images, and it looks like the beach ball is caused by unnecessary UI updates when you select or deselect images. I'll look into this for the next update.
If the exposure date/time is displayed correctly in the inspector, then you are probably sorting by import date/time, not exposure date/time. See the sort dropdown.
The number of selected images you can see in the browser. For the total duration calculation Observatory excludes rejected images, so it's not exactly the same. I can add the number used for the total duration calculation in the next update.
If the exposure date/time is displayed correctly in the inspector, then you are probably sorting by import date/time, not exposure date/time. See the sort dropdown.
The number of selected images you can see in the browser. For the total duration calculation Observatory excludes rejected images, so it's not exactly the same. I can add the number used for the total duration calculation in the next update.