Closed gpassera closed 8 months ago
mworion
commented
8 months ago Hi Giuseppe, this happens when MW4 tries to start a plate solve and somethings happens in between. Then MW4 is not able to sync modeling process between the different running threads. I try to find out, what happened in calling the solver. I have never seen this before. If you don't mind, please update to the latest beta. With NINA I would do modeling timing to conservative if you are more in progressive now. Michel
gpassera
commented
8 months ago Michel Thank you for your answer. I will do what you suggest. If it could help , the issue is present only in binning 1 and not in binning 2. Thank you Regards Giuseppe
Giuseppe Passera www.giuseppepassera.com
Il giorno sab 13 gen 2024 alle 21:43 Michael @.***> ha scritto:
Hi Giuseppe, this happens when MW4 tries to start a plate solve and somethings happens in between. Then MW4 is not able to sync modeling process between the different running threads. I try to find out, what happened in calling the solver. I have never seen this before. If you don't mind, please update to the latest beta. With NINA I would do modeling timing to conservative if you are more in progressive now. Michel
— Reply to this email directly, view it on GitHub https://github.com/mworion/MountWizzard4/issues/344#issuecomment-1890764594, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKUSVCJZIU6EZYZTPJLW6JTYOLWYTAVCNFSM6AAAAABBZQPIJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJQG43DINJZGQ . You are receiving this because you authored the thread.Message ID: @.***>
gpassera
commented
8 months ago Btw, the issue can be closed. Thank you very much. Giuseppe
Giuseppe Passera www.giuseppepassera.com
Il giorno dom 14 gen 2024 alle 18:00 Giuseppe Passera @.***> ha scritto:
Michel Thank you for your answer. I will do what you suggest. If it could help , the issue is present only in binning 1 and not in binning 2. Thank you Regards Giuseppe
Giuseppe Passera www.giuseppepassera.com
Il giorno sab 13 gen 2024 alle 21:43 Michael @.***> ha scritto:
Hi Giuseppe, this happens when MW4 tries to start a plate solve and somethings happens in between. Then MW4 is not able to sync modeling process between the different running threads. I try to find out, what happened in calling the solver. I have never seen this before. If you don't mind, please update to the latest beta. With NINA I would do modeling timing to conservative if you are more in progressive now. Michel
— Reply to this email directly, view it on GitHub https://github.com/mworion/MountWizzard4/issues/344#issuecomment-1890764594, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKUSVCJZIU6EZYZTPJLW6JTYOLWYTAVCNFSM6AAAAABBZQPIJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJQG43DINJZGQ . You are receiving this because you authored the thread.Message ID: @.***>
mworion
commented
8 months ago Giuseppe, thanks for all the effort of testing. You comment on binning helps as bin1 does bring more load to the system (much more data to be handled). I intend to smoothen this process with some refactoring and some hint for the users. ASTAP as well as modeling only needs 1500 px each axis to be good. So binning is a good way to improve speed overall. Closing this issue, but please report back if you see more of this. Michel
gpassera
commented
8 months ago Michel
mine MW4 was already set to conservative. If I remember well in some past version of MW there was the possibility of setting a waiting time after the mount reached the position before initiating the exposure. Speaking with 10micron, this option would be useful to allow the mount to position itself optimally before starting the exposure. It could also be set a post-exposure timeout to give time to not particularly fast cameras to fully download the image before solving. Hope this help Regards
Giuseppe
On Sun, Jan 14, 2024 at 6:38 PM Michael @.***> wrote:
Giuseppe, thanks for all the effort of testing. You comment on binning helps as bin1 does bring more load to the system (much more data to be handled). I intend to smoothen this process with some refactoring and some hint for the users. ASTAP as well as modeling only needs 1500 px each axis to be good. So binning is a good way to improve speed overall. Closing this issue, but please report back if you see more of this. Michel
— Reply to this email directly, view it on GitHub https://github.com/mworion/MountWizzard4/issues/344#issuecomment-1891014466, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKUSVCO7PITSPIAAPWOQLLTYOQJYZAVCNFSM6AAAAABBZQPIJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJRGAYTINBWGY . You are receiving this because you authored the thread.Message ID: @.***>
-- Giuseppe Passera www.giuseppepassera.com
mworion
commented
8 months ago Giuseppe,you will find this option under Mount Settings. There is an explicit wait time before exposing during modeling, which is independent from any setting in the mount.Post Exposure should be not an issue as long if the camera drivers report their status correct. There is a state downloading. MW4 respects this state and wait for downloaded the image. Conservative means MW4 wait until the image is save onto the disk.MichelAm 15.01.2024 um 10:15 schrieb gpassera @.***>: Michel
mine MW4 was already set to conservative.
If I remember well in some past version of MW there was the possibility of
setting a waiting time after the mount reached the position before
initiating the exposure.
Speaking with 10micron, this option would be useful to allow the mount to
position itself optimally before starting the exposure. It could also be
set a post-exposure timeout to give time to not particularly fast cameras
to fully download the image before solving.
Hope this help
Regards
Giuseppe
On Sun, Jan 14, 2024 at 6:38 PM Michael @.***> wrote:
Giuseppe,
thanks for all the effort of testing. You comment on binning helps as bin1
does bring more load to the system (much more data to be handled).
I intend to smoothen this process with some refactoring and some hint for
the users. ASTAP as well as modeling only needs 1500 px each axis to be
good. So binning is a good way to improve speed overall.
Closing this issue, but please report back if you see more of this.
Michel
—
Reply to this email directly, view it on GitHub
https://github.com/mworion/MountWizzard4/issues/344#issuecomment-1891014466,
or unsubscribe
.
You are receiving this because you authored the thread.Message ID:
@.***>
--
Giuseppe Passera
www.giuseppepassera.com
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: @.***>
gpassera
commented
8 months ago Michel thank you, there are so many options.. :) I will try.
Thank you Giuseppe
On Mon, Jan 15, 2024 at 10:21 AM Michael @.***> wrote:
Giuseppe,you will find this option under Mount Settings. There is an explicit wait time before exposing during modeling, which is independent from any setting in the mount.Post Exposure should be not an issue as long if the camera drivers report their status correct. There is a state downloading. MW4 respects this state and wait for downloaded the image. Conservative means MW4 wait until the image is save onto the disk.MichelAm 15.01.2024 um 10:15 schrieb gpassera @.***>: Michel
mine MW4 was already set to conservative.
If I remember well in some past version of MW there was the possibility of
setting a waiting time after the mount reached the position before
initiating the exposure.
Speaking with 10micron, this option would be useful to allow the mount to
position itself optimally before starting the exposure. It could also be
set a post-exposure timeout to give time to not particularly fast cameras
to fully download the image before solving.
Hope this help
Regards
Giuseppe
On Sun, Jan 14, 2024 at 6:38 PM Michael @.***> wrote:
Giuseppe,
thanks for all the effort of testing. You comment on binning helps as bin1
does bring more load to the system (much more data to be handled).
I intend to smoothen this process with some refactoring and some hint for
the users. ASTAP as well as modeling only needs 1500 px each axis to be
good. So binning is a good way to improve speed overall.
Closing this issue, but please report back if you see more of this.
Michel
—
Reply to this email directly, view it on GitHub
< https://github.com/mworion/MountWizzard4/issues/344#issuecomment-1891014466>,
or unsubscribe
.
You are receiving this because you authored the thread.Message ID:
@.***>
--
Giuseppe Passera
www.giuseppepassera.com
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/mworion/MountWizzard4/issues/344#issuecomment-1891650273, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKUSVCOLC443HSYPNR6CRBTYOTYH5AVCNFSM6AAAAABBZQPIJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJRGY2TAMRXGM . You are receiving this because you authored the thread.Message ID: @.***>
-- Giuseppe Passera www.giuseppepassera.com
Hi Michel
running the model creation in binning 1 I got "Build error - Out of sync exception" I presume the error is raised by the following condition
2024-01-13 18:45:56.064][I][ runBasic.py][ 163] Solving image-003: [2024-01-13 18:45:56.065][W][ plateSolve.py][ 274] Image file not found: C:\MW4/image/m-2024-01-13-18-44-29-med/image-003.fits File image-003.fits is present. Any idea? Thanks and regards mw4-2024-01-13.log