It seems that the issue occurs specifically when the EZ script instance is run in the global context (as opposed to the direct context or view target context).

PixInsight: EZ Processing Suite - the suite for your processing needs
#176
Posted 25 October 2021 - 09:28 PM
#177
Posted 26 October 2021 - 05:39 AM
This is such a wonderful set of tools. Only I have is praise for them and my thanks to all the hours of work put into this by the creators.
I would ask for one thing. I use it so often that I wish I could process multiple images one after the other unattended instead of one at a time.
- crackout likes this
#178
Posted 26 October 2021 - 06:13 AM
I would ask for one thing. I use it so often that I wish I could process multiple images one after the other unattended instead of one at a time.
Yes, this would be really nice to have.
Queue up a bunch of images for denoise and let it run over night for example.
#179
Posted 26 October 2021 - 09:54 AM
This is such a wonderful set of tools. Only I have is praise for them and my thanks to all the hours of work put into this by the creators.
I would ask for one thing. I use it so often that I wish I could process multiple images one after the other unattended instead of one at a time.
I would second the praise this tool. thank you very much for the work to make it available.
#180
Posted 26 October 2021 - 12:17 PM
I also don't know what the issue might be why the script running through a process icon disables undo, I wouldn't know what could cause this.
Looks like EZ_Common.js does not comply with the fundamental PJSR requirement to surround processing with View.beginProcess() and View.endProcess(). MR submitted.
#181
Posted 26 October 2021 - 03:57 PM
Question- I apologize if this is a dumb question- Is StarNet++ the same as the Starnet tab listed in PI? I have been hesitant to download StarNet++ because of not being sure if these are the same or different functions.
Best,
Brian
Edited by Dark_Knight18, 26 October 2021 - 03:58 PM.
#182
Posted 26 October 2021 - 05:28 PM
yes it is.
StarNet was first developed as a python program by Nikita, then when he ported it to C, he called it StarNet++ to distinguish it. at some point Nikita re-wrote it as a PI process, which i think was also called StarNet++.
at some point Juan (PI developer) picked up the code and refactored it a little bit, and decided to call it just "StarNet".
so you don't need to download anything, it's now distributed as part of PixInsight.
rob
#183
Posted 30 October 2021 - 06:08 PM
Hi all
New to the EZ suite (and PI in general). Trying to figure out why I can't (or should even be able to) see a difference when using the EZ Decon script.
If I understand correctly, when I click "evaluate EZ Decon Run" it should give me a preview of what the image will look like in a new tab. I can then compare the before/after between that and the original image.
However, I'm not seeing any difference, even when I play around with the iterations. Have I understood this correctly?
Here's an example. There's no difference that I can see.
Before:
After:
- Hobby Astronomer likes this
#184
Posted 31 October 2021 - 04:24 PM
If I understand correctly, when I click "evaluate EZ Decon Run" it should give me a preview of what the image will look like in a new tab. I can then compare the before/after between that and the original image. However, I'm not seeing any difference, even when I play around with the iterations. Have I understood this correctly?
You understand correctly. The difference is usually really quite subtle, but you should see it in certain regions. When it's too much, you'll see "ringing" around stars, often within the brighter parts of the nebula. I confirm I'm not seeing any difference in your two examples, except for the correct tab switch. Did you perhaps mask too much? Let's see your mask.
#185
Posted 07 November 2021 - 09:04 AM
You understand correctly. The difference is usually really quite subtle, but you should see it in certain regions. When it's too much, you'll see "ringing" around stars, often within the brighter parts of the nebula. I confirm I'm not seeing any difference in your two examples, except for the correct tab switch. Did you perhaps mask too much? Let's see your mask.
Not sure why I didn't get a quote notification, but thanks.
Indeed, it was my star mask. I had to play around with it to see any differences. It's subtle but I got it working
Now if only we could use GPU acceleration on the de-noise algorithm!
- dswtan likes this
#186
Posted 17 January 2022 - 04:31 PM
Hi everyone - my first post, putting here because it is about EZ Processing Suite. I have Pixinsight 1.8.8-12 loaded on a fully loaded Mac Pro running Big Sur. What I have noticed is sporadic crashing or freezing of Pixinsight when I am running EZ Soft Stretch. Sometimes it works fine, sometimes justing calling it up crashes Pixinsight, and sometimes calling it up results in the attached partial Soft Stretch dialog box and a freezing of Pixinsight. I have been working with FITS files from the Hubble and Chandra, but today Soft Stretch has consistently crashed or frozen the app when I try to use it.
Does anyone have a similar issue, or any potential solutions. And yes, I have deleted and reinstalled EZ Processing Suite.
I have attached a screen shot of the partial dialog box that appears when Pixinsight freezes (as opposed to crashing!!).
Thanks!
#187
Posted 17 January 2022 - 04:57 PM
To be more specific, these are the files that are crashing EZ Soft Stretch (they stretch just fine in FITS Liberator). They are at the Chandra X-ray telescope archive site:
https://chandra.harv...ength_data.html
If you look at the files for NGC 1929, there are three FITS files: a X-ray file, an IR file and an optical file.
When I use Soft Stretch with the IR file, it works just fine. When I try to stretch the X-ray or optical files, this leads to either a freeze or an outright crash.
I seem to have no issues when I use Soft Stretch with Hubble drz FITS files, just the rare crash. So there is something going on with some of these files that causes crashing.
Thanks if you have any ideas......other than "don't use the Chandra files"!
#188
Posted 17 January 2022 - 07:12 PM
I reproduced your problem with the _xray file. Macbook Pro (2019) w/64GB memory running macOS Monterey, PI 1.8.8-12, and EZ Soft Stretch v 0.11.
- Kailas likes this
#189
Posted 17 January 2022 - 08:31 PM
Thanks, Ranger - at least now I know it isn't something specific to my setup. I guess I will have to stick with Hubble drz files for the time being.
#190
Posted 17 January 2022 - 08:39 PM
I've seen it happen when the calculations fail, try manually stretching the image just a little first.
#191
Posted 17 January 2022 - 09:25 PM
Thanks, Explorer. I tried to stretch with HistogramTransformation first just now, and then calling up EZ freezes Pixinsight. There is something odd about some of these files, because this doesn't happen with most of the files I download from Hubble Archive. The Space Telescope filing systems are a rat's nest, so who knows. But it sure would be nice to reliably combine Chandra, Hubble and other data.
#192
Posted 24 January 2022 - 06:54 PM
I have been using ExProcessing for a few days now, I had saved my project a few times, and keep moving on, today pix just vanished, when I open my projects are one, EZ processing suite is not there but if I view updates it thinks its installed al though its not.
Any pointers there I can't be only guy this happen too,
thanks
#193
Posted 25 January 2022 - 10:52 AM
Script > Feature Scripts > Add, navigate to PI script folder, click OK, check that PI hasn't doubled up all the scripts in the dialog. if not, click OK.
rob
- Raginar likes this
#194
Posted 11 May 2022 - 05:52 AM
First of all: thank you so much for these tools! I can't live without them.
I am running into a time issue with EZ Deconv PSF generation. I am working on a mosaic and the star count is over 30,000. PSF generation runs quickly enough when it detects 2,000 or less stars but now it's been running for hours without a result in this crowded star field. There are two controls in the PSF generation window. Sensitivity and Max PSF stars (default 50). Can I use those controls to speed up the process? How do I do that?
#195
Posted 11 May 2022 - 05:54 AM
What I usually do is clone a portion of the main image with representative stars, and run just the psf generation portion. This produces a new image. Then start over with the full image, and instead of generating a new PSF image select the view from the first partial run.
- Shinken and jonnybravo0311 like this
#196
Posted 19 May 2022 - 09:19 AM
I am unable to find a site to download the PI EZ Processing Suite. Has darkarchon withdrawn the tools? None of the links I was able to find in this thread seemed to go to a download site.
CS, Rod Michael
Edited by rodmichael, 19 May 2022 - 03:48 PM.
#197
Posted 19 May 2022 - 11:11 AM
https://darkarchon.i...et-box.ch:8443/
seems to be working, at least from my corner of the internet. you don't download it straight from there, you make a new entry in PI's "manage repositories" dialog box and then ask PI to check for updates.
rob
#198
Posted 19 May 2022 - 03:47 PM
Thank you, pfile. A fundamental misunderstanding on my part.
However, when I went to install the suite, I was notified that the software doesn't have a valid "Signature." Should I be concerned?
CS, Rod Michael
Edited by rodmichael, 19 May 2022 - 03:49 PM.
#199
Posted 19 May 2022 - 06:28 PM
No, I just won't sign the scripts because I don't want to follow the whims of an effort to close down the free scripts ecosystem. As long as the scripts load and work I will not sign them out of spite for the reasons why the PI devs decided to implement this system to begin with.
However this is not the time or place to debate this. Long story short, my scripts are safe, people have been using them for years now even before the whole signing shenanigans started to happen. Nothing changed on my part and nothing will change as long as the signing remains optional.
- lambermo, tkottary and ezwheels like this
#200
Posted 20 May 2022 - 02:40 PM
No, I just won't sign the scripts because I don't want to follow the whims of an effort to close down the free scripts ecosystem. As long as the scripts load and work I will not sign them out of spite for the reasons why the PI devs decided to implement this system to begin with.
However this is not the time or place to debate this. Long story short, my scripts are safe, people have been using them for years now even before the whole signing shenanigans started to happen. Nothing changed on my part and nothing will change as long as the signing remains optional.
Darkarchon, Do you have plans to use Starnet 2 version with the suite?