1.7.443 SuperStructure colored quadrents

[elf]

Hi, I am still noticing that in SuperStructure with brightness retention off, I get an image with slightly different shading in each quadrant, recursively. It makes everything look like a mosaic of slightly colored quadrant tiles.
I noticed this in 1.7.443, 1.7.438, and 1.7.434. (these are the only ones I have tried in this range)
Am I missing something?

Screen Shot 2020-11-14 at 3.03.12 AM.jpg (232.14 KiB) Viewed 6876 times

[admin]

Hi,

I thought this was solved in 1.7.443...
Can you kindly let me know your specs?

• Operating system
• GPU (as found in the About dialog of StarTools)
• Size (x * y) of the dataset you are trying to process

Does the issue happen on smaller datasets (say < 1000 x 1000 pixels)?

Thank you!

[elf]

Hi Ivo,

2020 27" iMac, 128gb
MacOS Catalina 10.15.6
CPU with 20 logical cores
AMD Radeon Pro 5700XT Compute Engine with 40 compute units

The source FITS appears to be 6069x3958 (inferred from AutoDev params)
The most recent affected result was seen after bin50% to 3034x1979
My previous attempts were after bin25% to 1517x989

At your request I just tested bin16.37% to 993x647, and do not see this artifact occurring at this smaller resolution.

(side comment - soooo much faster to process at lower res!)
Thanks for checking into this!

[elf]

I did just notice something else however -

After my test, i cancelled the SuperStr, and Undid the Color module.
Redid the color module with different settings (slightly different RGB reduce, lowered the bright and dark sat, raised the overall saturation.), then back to the SuperStr, brightness retention off. Everything was much darker than I expected, and adjusting the Strength, I noticed a HUGE jump just between 100% and 99%, and adjusting less than 99% seemed to do nothing at all, while still a huge difference between 99-100. above 100 did seem to still have an effect (though I'm not sure how that works honestly, always appears to me to do something similar to gamma, and seemingly starts to invert colors or something in the high ranges)

Anyhow I wanted to mention this because it appears it might also be a (related? unrelated?) bug?

[admin]

I did just notice something else however -

After my test, i cancelled the SuperStr, and Undid the Color module.
Redid the color module with different settings (slightly different RGB reduce, lowered the bright and dark sat, raised the overall saturation.), then back to the SuperStr, brightness retention off. Everything was much darker than I expected, and adjusting the Strength, I noticed a HUGE jump just between 100% and 99%, and adjusting less than 99% seemed to do nothing at all, while still a huge difference between 99-100. above 100 did seem to still have an effect (though I'm not sure how that works honestly, always appears to me to do something similar to gamma, and seemingly starts to invert colors or something in the high ranges)

Anyhow I wanted to mention this because it appears it might also be a (related? unrelated?) bug?

Thank you for all this (and apologies for the slight delay in getting back to you - been wrangling Big Sur into submission... )

I'm rather lost with regards to this strange behavior.

Right now the behavior of your configuration appears to be an anomaly across all other platform/GPU combinations. Other users on macOS with Navi-based GPUs no longer report the "quadrant" issue as of 1.7.443, and I can no longer replicate it myself.
The Strength parameter behavior is even stranger and I have not heard of this issue before.

Can you see any GPU driver issues in the System Log?

Have you got any other applications or benchmarks that can stress your GPU?

[elf]

So I ran things again and copied the console output filtered for "GPU" (not sure if there is a better search/filter to use?)

Loaded fits.
Autodev.
Bin 50%.
Wipe.
Autodev.
Contrast.
HDR.
Sharp.
Color.
SuperStr. Turned Brightness Retention Off. Verified the same quadrant issue was happening (Yep).
Canceled SuperStr.
Undo (Undid the Color).
Color. (similar params, just reduced reds mostly, and a little blue)
SuperStr. Brightness retention selection now seems to have no effect on the image. Slider seems to have mostly no effect, but with it up very high (over 300%) it starts to show some effect seemingly on the bright reds.

so the console output below (filtered for keyword "GPU") is from the time period of the above, so it includes the mosaic pattern issue as well as the subsequent issues with seeing any difference with the brightness retention setting and the strength slider.

Is there a different thing I should try to filter for in the console? I'm afraid the console spits so much out it feels like it would generate a whole encyclopedia in a sessions time.

Code: Select all

default	18:00:29.463495-0800	runningboardd	[daemon<com.apple.coreservices.uiagent(502)>:77169] Ignoring GPU update because this process is not GPU managed
default	18:00:29.572587-0800	runningboardd	[daemon<com.apple.coreservices.uiagent(502)>:77169] Ignoring GPU update because this process is not GPU managed
default	18:00:30.903060-0800	runningboardd	[application<com.apple.news(502)>:77375] Set GPU priority to "deny"
default	18:00:31.452404-0800	runningboardd	Acquiring assertion targeting application<com.apple.news(502)> from originator [daemon<com.apple.uikitsystemapp(502)>:31345] with description <RBSAssertionDescriptor; FBApplicationProcess; ID: 330-31345-4295; target: 77375> attributes = {
    <RBSRunningReasonAttribute: 0x7f8f3a12b5e0; runningReason: 10000>;
    <RBSPreventIdleSleepGrant: 0x7f8f3a129880>;
    <RBSDefineRelativeStartTimeGrant: 0x7f8f3a1245d0>;
    <RBSGPUAccessGrant: 0x7f8f3a11a510>;
    <RBSCPUAccessGrant: 0x7f8f3a110940; role: Background>;
}
default	18:00:31.452811-0800	runningboardd	[application<com.apple.news(502)>:77375] Set GPU priority to "allow"
default	18:00:31.585561-0800	runningboardd	Acquiring assertion targeting application<com.apple.news(502)> from originator [daemon<com.apple.uikitsystemapp(502)>:31345] with description <RBSAssertionDescriptor; "FBScene (BackgroundActive) <C4E8E3E8-DB24-4A53-A45C-8065B1A26F8F>"; ID: 330-31345-4298; target: 77375> attributes = {
    <RBSRunningReasonAttribute: 0x7f8f3a3253f0; runningReason: 10001>;
    <RBSDefineRelativeStartTimeGrant: 0x7f8f3a326a80>;
    <RBSGPUAccessGrant: 0x7f8f3a334b30>;
    <RBSCPUAccessGrant: 0x7f8f3a32e770; role: NonUserInteractive>;
    <RBSJetsamPriorityGrant: 0x7f8f3a309170; priority: Background>;
    <RBSDurationAttribute: 0x7f8f3a333de0; invalidationDuration: 20.00; warningDuration: 0.00; startPolicy: Fixed; endPolicy: Invalidate>;
    <RBSResistTerminationGrant: 0x7f8f3a324db0; terminationResistance: NonInteractive>;
}
default	18:00:32.572676-0800	runningboardd	[application<com.apple.news(502)>:77375] Set GPU priority to "deny"
default	18:00:49.996189-0800	kernel	[AGPM][ERROR][BOOST       ][setBoost                ] 0 fGPUIdleIntervalMS = 0, ControlID = 17
default	18:01:05.154437-0800	runningboardd	[executable<StarTools(502)>:77392] Ignoring GPU update because this process is not GPU managed
default	18:01:05.193808-0800	runningboardd	[executable<StarTools(502)>:77392] Ignoring GPU update because this process is not GPU managed
default	18:01:05.260813-0800	runningboardd	[executable<Console(502)>:77372] Ignoring GPU update because this process is not GPU managed
default	18:01:17.828505-0800	runningboardd	[xpcservice<com.apple.appkit.xpc.openAndSavePanelService(502)>:77396] Ignoring GPU update because this process is not GPU managed
default	18:01:17.959111-0800	runningboardd	[executable<QuickLookUIService(502)>:77397] Ignoring GPU update because this process is not GPU managed
default	18:01:18.618484-0800	runningboardd	[xpcservice<com.google.GoogleDrive.FinderSyncAPIExtension(502)>:77407] Ignoring GPU update because this process is not GPU managed
default	18:01:21.961246-0800	runningboardd	[xpcservice<com.google.GoogleDrive.FinderSyncAPIExtension(502)>:77416] Ignoring GPU update because this process is not GPU managed
default	18:01:22.166246-0800	runningboardd	[daemon<com.apple.quicklook.ui.helper(502)>:77417] Ignoring GPU update because this process is not GPU managed
default	18:05:23.059458-0800	runningboardd	[xpcservice<com.apple.WebKit.WebContent(502)>:77327] Ignoring GPU update because this process is not GPU managed
default	18:05:23.079864-0800	runningboardd	[xpcservice<com.apple.WebKit.WebContent(502)>:75244] Ignoring GPU update because this process is not GPU managed
default	18:07:21.100986-0800	runningboardd	[daemon<com.bjango.istatmenus.status(502)>:71597] Ignoring GPU update because this process is not GPU managed
default	18:07:21.200732-0800	runningboardd	[executable<StarTools(502)>:77392] Ignoring GPU update because this process is not GPU managed
default	18:07:26.856355-0800	runningboardd	[executable<StarTools(502)>:77392] Ignoring GPU update because this process is not GPU managed
default	18:07:26.957806-0800	runningboardd	[daemon<com.bjango.istatmenus.status(502)>:71597] Ignoring GPU update because this process is not GPU managed
default	18:09:05.306569-0800	runningboardd	[application<com.apple.news(502)>:77519] Set GPU priority to "deny"
default	18:09:05.732567-0800	runningboardd	Acquiring assertion targeting application<com.apple.news(502)> from originator [daemon<com.apple.uikitsystemapp(502)>:31345] with description <RBSAssertionDescriptor; FBApplicationProcess; ID: 330-31345-4322; target: 77519> attributes = {
    <RBSRunningReasonAttribute: 0x7f8f3a125c80; runningReason: 10000>;
    <RBSPreventIdleSleepGrant: 0x7f8f3a125080>;
    <RBSDefineRelativeStartTimeGrant: 0x7f8f3a12f6e0>;
    <RBSGPUAccessGrant: 0x7f8f3a11a6e0>;
    <RBSCPUAccessGrant: 0x7f8f3a12efc0; role: Background>;
}
default	18:09:05.732950-0800	runningboardd	[application<com.apple.news(502)>:77519] Set GPU priority to "allow"
default	18:09:05.806437-0800	runningboardd	Acquiring assertion targeting application<com.apple.news(502)> from originator [daemon<com.apple.uikitsystemapp(502)>:31345] with description <RBSAssertionDescriptor; "FBScene (BackgroundActive) <C4E8E3E8-DB24-4A53-A45C-8065B1A26F8F>"; ID: 330-31345-4325; target: 77519> attributes = {
    <RBSRunningReasonAttribute: 0x7f8f37c3f9f0; runningReason: 10001>;
    <RBSDefineRelativeStartTimeGrant: 0x7f8f37c3ee90>;
    <RBSGPUAccessGrant: 0x7f8f37c32d90>;
    <RBSCPUAccessGrant: 0x7f8f37c3f090; role: NonUserInteractive>;
    <RBSJetsamPriorityGrant: 0x7f8f37c40b50; priority: Background>;
    <RBSDurationAttribute: 0x7f8f37c405b0; invalidationDuration: 20.00; warningDuration: 0.00; startPolicy: Fixed; endPolicy: Invalidate>;
    <RBSResistTerminationGrant: 0x7f8f37c38920; terminationResistance: NonInteractive>;
}
default	18:09:06.844723-0800	runningboardd	[application<com.apple.news(502)>:77519] Set GPU priority to "deny"
default	18:11:59.235287-0800	kernel	[AGPM][ERROR][BOOST       ][setBoost                ] 0 fGPUIdleIntervalMS = 0, ControlID = 17
default	18:12:01.033236-0800	runningboardd	[executable<Console(502)>:77372] Ignoring GPU update because this process is not GPU managed
default	18:12:01.138145-0800	runningboardd	[executable<StarTools(502)>:77392] Ignoring GPU update because this process is not GPU managed
default	18:12:55.309525-0800	runningboardd	[executable<StarTools(502)>:77392] Ignoring GPU update because this process is not GPU managed
default	18:12:55.417495-0800	runningboardd	[executable<Console(502)>:77372] Ignoring GPU update because this process is not GPU managed
default	18:13:55.520558-0800	kernel	[AGPM][ERROR][BOOST       ][setBoost                ] 0 fGPUIdleIntervalMS = 0, ControlID = 17
default	18:13:56.839401-0800	runningboardd	[executable<Console(502)>:77372] Ignoring GPU update because this process is not GPU managed
default	18:13:56.940057-0800	runningboardd	[executable<StarTools(502)>:77392] Ignoring GPU update because this process is not GPU managed

[admin]

Thank you for attaching that. I don't think there is anything strange in there.

When the issue happens, would you be able to let it complete, and then use the slider control to set the Airy Disk Radius parameter to, say, 25%? If this yields a correct image, and you can set it back to 50% and that yields a correct image too, then I might have a better idea where to look...

[admin]

Seems like this bug is a never ending saga.

I found a potential zeroing out bug that definitely has the potential to lead to misbehavior and garbage. I fixed it in the latest beta 1.7.448.

For anyone still experiencing glitches, please give this version a try. Fingers crossed this version fixes all remaining issues.