LaCebra

Hello, Of course the problem described below can be compensated with StarAlignment, then DynamicCrop... however the problem would deserve an explanation for me. I photograph NGC 6853 on October 16, 2019, then the next day, at the same time, with the same filter, and the counterweights in the same direction. Sequence uses MLPT for each series of shots, with a residual error of less than 1 arcsec. The file NGC 6853.trg contains the coordinates of the target: - RA 20h 00m 29s - DEC +22° 47' 00" On October 16th ImageSolver + FITS Header give me the coordinates of the center of the image: - OBJCTRA 19h 59m 39s (angular error 00° 12' 30") - OBJCTDEC +22° 43' 31" (angular error 00° 03' 29") October 17 - OBJCTRA 19h 59m 27s (angular error 00° 15' 30") - OBJCTDEC +22° 42' 38" (angular error 00° 04' 22") 1 - Images are not centered on the position specified in NGC 6853.trg 2 - Between October 16 and 17, the images are, in addition, frankly shifted between them. This is where the problem arises for me: - delta RA 00° 03' 00" - delta DEC 00° 00' 00' 53" If someone can help me understand this both problems… La Cebra

Indeed, Sequence requires that the "d" be used, in order to specify the value of DEC rather than to comply with the international standard "°"

Your problem seems so big (as an exception!) that it could well be hidden in a configuration file, so not very far away... There are still others to explore next (with the list of filters for example). Tonight, heavy rain ongoing. So I don't touch the telescope computer. Tomorrow, I think. Good luck tonight.

1/ "Details " Click in the window messages Ctrl+A (select all) Ctrl+C (copy) NotePad : Ctrl+V (Paste) 2/ Please : The file .trg (target) 3/ Save the sequence before "Run Now" Copy here the code of the .seq file (sequence) With this three items I can replicate your situation, here or no ! I hope you are gradually learning French written in English words. La Cebra

I have a lot of trouble reading the screenshot. It's too fuzzy! But I think I can guess a well-known exception message: "Index was outside of the bounds of the array" (Please specify the exact text). It would also be interesting to know the list of messages located in "Details" When several tasks are to be performed consecutively (Luminance x 10, Red x 10, Green x10, Green x10, Blue x 10, Ha x 10) they are placed in an "container" in RAM memory. The above container should have 5 positions, for all 5 tasks. These tasks are numbered from 0 to 4. (computer scientist's secret, we start counting from zero ) If the form is misfilled/completed (by you) the pointer (index) of the task to be executed may be outside the range 0-4 (out of bounds). The program cannot perform an imaginary task that is outside the container. The index can, for example, have the value 7!!!!! Why not, but unlikely. ? The most likely is that it contains the value -1 (no data in the form). I seem to have specified that a filter was missing in one of your exp files. In this case the value would therefore be -1 This causes an exception... and P. Keller did not write a manager for this exception at this location in order to avoid this catastrophe!!!!! It is now necessary to verify that what I imagine with this some information corresponds well to the reality. I am still working on explaining "What unmanaged exceptions are ?", but there was a week of clear nights with a rather weak seeing. La Cebra

Hello Dave, I would like to read the contents of the files you are currently using: 1 - All night tasks The one with a ".sqe" extension in ProgramData\ASA\Sequence\ExposureSettings (for me at home ExposureFiles) 2 - Task details for each line of the previous file (.sqe) So, the one with a ".exp" extension in ProgramData\ASA\ASA\Sequence\ExposureSettings You can use private messaging (MP) La Cebra

What I'm saying here is not necessarily the same problem as you... But near... AutoSlew uses a PID (proportional, integral, derivative controller) to quickly move the mount, then slow down when approaching its target, without exceeding it. This PID must be adjusted (with difficulty) according to the load of the mount, and the position of its barycenter. For me it's almost impossible! Almost in the direction of the North Star, the mount starts to rumble, shake, jump. I can hear it all the way into the house. Bearings, encoders? I have to permanently slow down the mount to 25% of its "commercial" speed to limit the problem. This is at the origin of loosening the primary mirror by the violence of vibrations. AstroSystem was informed in writing in October 2018. Answer "I'm on a trip abroad". Maybe for Christmas 2019? Or 2020??? These vibrations, blockages, cause the PID to "stall" (like 737-Max ) about once a night. He can't move the mount to his target. This also results in a stop of tracking and the stars become long lines. A image losted. But when it comes to moving to a star, the mount stops along the way. When it comes to the realization of MLPT, often from the first view, the plot of the curve is impossible, and so is MLPT. All the images in the series are then lost. It is necessary to monitor at the top of AutoSlew if the sidereal tracking indicator remains active, otherwise it becomes a terrestrial tracking. But I don't have any unmanaged exceptions. Sequence continues as if nothing happened. I don't know if it's the same problem as you? If some of the terms I use are mistranslated, don't hesitate to ask me to clarify their meaning. La Cebra (Translated with www.DeepL.com/Translator)

- Is it possible to get your old computer back to work with your old configuration? - The unmanaged exception appears from the first image, or later in the series? - This night I got an unmanaged exception "Exposure Aborted". Fortunately I hadn't gone to sleep yet. I started again and everything worked until 6:00. The exception window does not allow me to identify the origin of this error.... ForwardCallToInvokeMember : camera, mean, software, MaxIm, operating system, hub USB, NAS... (in French "à" indicates the place where the action takes place.) System.Runtime.InteropServices.COMException (0x0000FFFF): Exposure Aborted à System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData) à MaxIm.CCDCameraClass.get_ImageReady() à Sequencer.RunSequence.StartSequence() à Sequencer.frmSequenceRun.cmdRun_Click(Object sender, EventArgs e) à System.Windows.Forms.Control.OnClick(EventArgs e) à System.Windows.Forms.Button.OnClick(EventArgs e) à System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) à System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) à System.Windows.Forms.Control.WndProc(Message& m) à System.Windows.Forms.ButtonBase.WndProc(Message& m) à System.Windows.Forms.Button.WndProc(Message& m) à System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Hello, I am writing the memo to help understand what the exceptions are, and how to live with them without anxiety. I think I'll end this Sunday. Maybe I will send a PDF copy to P. Keller If someone could make a similar memo about Quality Insurance, it would also be beneficial. I don't know enough about it. Finally, for those who have a perfect know how of mechanical design, a third memo would be welcome… When there are hexagonal screws BTR under the mount with a 6mm high head, the well that should hide this head screw should not be 6mm too, but 6.8 or 7mm (?). The height of the screw heads is standardised, but each manufacturer is obliged to stamp its own mark on the head for reasons of legal traceability (in the event of an accident). After this striking, the rise of the chased metal modifies the height of some screw heads, which goes from 6mm to 6.3mm... That's the way it is in The Real Life. When adjusting the azimuth mount there is therefore 0.3mm of stainless steel protruding and scraping on the aluminium of the support. Stainless steel wins! The mount jumps when the aluminum gives way, and the star suddenly passes to the other side of the target! P. Keller works in mechanics, computer programming, like me I write English All this is a lot of amateurism for a much more expensive equipment than the average. La Cebra

@George Thank you George, your method is even better @DaveS "why software should throw up unhandled exceptions at all..." I don't understand all the subtleties of English, and by far, so I answer below according to what I think understand... Two concepts must be separated: - the Sequence software cannot do otherwise than throw an exception in certain inconsistent situations! This is inevitable in "The Real Life". - P. Keller neglects to manage these exceptions. This is inexcusable. I will soon provide you with an explanation of what are .Net exceptions and how they are managed. Perhaps some will be interested? (P. Keller? ) La Cebra Translated with www.DeepL.com/Translator

(Translated with www.DeepL.com/Translator) 1 - Copying all windows of a screen: Print Screen key Copy of the active window only: Alt + Print Screen keys 2 - Unhandled Exception Errors: this message must never arrive on the user's screen. This is malpractice! So, write a one-page document about intercepting Try/Catch/Finally exceptions for .Net, then send it to P. Keller - Try: the portion of code you want to execute - Catch: the code to manage the exception(s) that may occur. This portion of code must make decisions in order to continue (without you!) the work as well as possible: start the task again, or move to the next image, or to the next object, or... The goal is not to stop the job (the images taken by the telescope while you are sleeping:)) - Finally: the code that must be executed after the Try, and possibly the Catch. To finish the job properly in both cases. 3 - Write a one-page document explaining that a Window form should only activate the Ok, Run, Go, Execute or any other button only after checking that all the necessary data has been entered and appears consistent. I have sometimes forgotten to designate the filter, or the number of frames to be taken, on one of the Sequence lines This must prevent much "Unhandled Exception Errors" during the night. 4 - If P. Keller does not succeed in achieving these two easy objectives, he will not be admitted to the final examinations for the Bac+2 course of study (basic programming technician). 5 - It was my job for ten years to train professional application designers with 5 years of higher education. It is clear that this person must go to training on this subjects, or, even better, entrust the specifications to an external company that will be able to do so properly. Right now it's just a shameful job! Dura lex sed lex.

Hello George, 1 - I have a definite advantage with C# - CSharpFITS I was able to extract the functions I needed, then decode line by line what needed to be done. And then I copied/reprogrammed as needed (store my Bias, Darks, Flats, Lights images in SQL-Server). I mean, I forgot everything It is frankly more difficult in Delphi where sources are scarcer. 2 - Can you publish one of these images in the cloud, describe the shooting (software, camera, etc.), and finally make a synthesis of your current analyses. I'm not sure I have an immediate answer, however.... 3 - Astronomical photography is of the same nature as Lucky Luke : A long and lonely journey La Cebra (Translated with www.DeepL.com/Translator)

@Waldemar No, it's CSharpFITS - a complete C# library to FITS (but with a little bug ) https://fits.gsfc.nasa.gov/fits_libraries.html#CSharpFITS DownLoad :http://voi.iucaa.in/voi/CSharpFITS.html

@George You can see that... https://fits.gsfc.nasa.gov/fits_libraries.html#delafits DeLaFits DeLaFits (free software, MIT License) is published on GitHub. DeLaFits is native for Delphi and Lazarus and is not a wrapper around another library. Features: building, reading, editing, and rendering of a FITS primary array image. DeLaFits supports only Single Image (one header and one data unit).

Hi George, Several years ago, I processed "fits" images in an elementary way (autostrech). For that I used a library of functions in C#, NASA origin (?) There was indeed a "bug" in their source code. After correction everything worked well. If necessary, I could look for these elements. Good luck with that. La Cebra

Hello, Tommy, It is important for a beginner (like me) to perceive the distance between what you know how to do and what I can do today (but also what I could do 4 years ago ) Here, I see cumulative exposure times of 10-20 hours, but how many years to learn to achieve this... ? Congratulations LaCebra As far as I'm concerned: "Fail. Fail again. Fail better" - Samuel Beckett

----- Français ----- L'alcool isopropylique ne nettoie pas, il ne sert qu'à remplacer l'eau au moment du séchage. Il est pulvérisé (en grande quantité) directement sur le miroir. Après, tout sèche et c'est terminé. La marque centrale n'est pas collée, ce soit être un dépôt d'encre par sérigraphie, ou bien un gravage au sable ou à l'acide fluorhydrique. Cette marque n'est pas altérée par le nettoyage. ----- English ----- Isopropyl alcohol does not clean, it is only used to replace water during drying. It is sprayed (in large quantities) directly on the mirror. Then, everything dries up and it's over. The central mark is not glued, it is either an ink deposit by screen printing, or a sand or hydrofluoric acid engraving. This mark is not altered by cleaning.

----- Français ----- Bonjour, Le miroir (300 mm) avait deux ans. Ici les problèmes viennent : De la poussière de schiste de la plantation d'avocatiers, de manguiers, d'oliviers ; Du pollen de ces arbres ; Des araignées qui tissent leur toile à l'intérieur du tube ; Des papillons nocturnes qui viennent s'y installer pour la journée ; De l'incendie qui a ravagé l'autre versant de la colline, juste après la livraison L du télescope ; La condensation matinale finie par coller le tout sur le miroir… J'ai suivi la notice AstroSysteme pour le nettoyage, avec quelques détails supplémentaires amenés par l'expérience : Eau désionisée 2.5 l ; Alcool isopropylique 1 l ; Faire quelques photos, afin de comparer AVANT et APRES, et en particulier l'étiquette latérale qui indique la focale réelle mesurée par le polisseur du miroir. Sur une de celles-ci on peut lire diam = 298 mm, et focale 1132 mm. Repérer aussi la position du miroir par rapport à sa cage de maintien, afin de ne pas avoir à toucher aux réglages des six vis latérale en nylon ; Ce miroir, de 300 mm, a été totalement démonté puis posé en pente sur la table de la terrasse ; Le temps était ensoleillé, mais le vent s'est levé en rafales dès que le miroir était mouillé (il faut regarder la météo avant donc) ; La première opération est nettoyer l'arrière du miroir, et sa tranche, afin que cette crasse ne revienne pas ensuite salir la face avant ; il fallait le vivre pour le comprendre J Pendant l'aspersion du miroir avec de l'eau et du Teepol, il faut détremper, puis attendre 5mn que tout ramollisse, ensuite arroser de nouveau et observer l'eau qui s'écoule en bas miroir. Au début c'est assez "chargé", puis l'eau redevient transparente avec simplement de nombreuses bulles J Il est alors temps de commencer à poser des feuilles de papier absorbant en aspergeant beaucoup, attendre, puis les décoller et les jeter. Rincer franchement, recommencer. Il ne faut pas tenter d'enlever tous les défauts, l'amélioration de l'image serait infinitésimale, et les risques trop sévères par contre ; donc accepter l'imperfection ; Pour moi c'était des débris de l'incendie avec du goudron qui sont venus vers le télescope une semaine après l'incendie. Je n'y ai pas touché ; Peut-être l'acétone serait plus adaptée pour dissoudre les goudrons ? Ensuite, les lingettes en microfibres nécessaires à la finition du travail sont tellement plus jolies de toutes les couleurs chez Amazon. Mais afin d'éviter une crise cardiaque il vaut mieux les laver (à la main) avant usage, afin qu'elle "dégorgent" leur couleur. Sinon on voit des filets colorés traverser le miroir tout propre. Il faut quand même détremper les lingettes avant usage. Donc ne pas utiliser une lingette lavée mais sèche, en pensant qu'elle absorbera plus… rayures possibles alors, car la lingette est "raide" ; Enfin, avec un papier absorbant, aspirer le bourrelet liquide d'alcool isopropylique qui s'accumule par gravité en bas miroir. Il suffit de le toucher sur la tranche du miroir pour qu'il disparaisse aussitôt. Ce n'est jamais rassurant de voir une lame liquide s'évaporer progressivement, en laissant éventuellement une marque. Remettre le miroir dans sa cage. Les trois pattes de maintien supérieur sont simplement posées sur le miroir, et maintenu légèrement avec un doigt de la main pendant le serrage de ses deux vis. Avant cette intervention, les pattes de maintien avaient une distance de 1 à 2 mm de jeu par rapport au miroir, et celui-ci faisait "Clong !" quand il basculait avec la monture. Maintenant ça va mieux… Comme mon explication est traduite avec DeepL tu peux la corriger en bon anglais, et la republier ici. Si certains veulent le faire en espagnol ce serait généreux aussi ----- (english) ----- Hello, The mirror (300 mm) was two years old. Here problems come: - Shale dust from the planting of avocado trees, mango trees, olive trees; - Pollen from these trees; - Spiders weaving their web inside the tube; - Butterflies that come to settle there for the day; - The fire that devastated the other side of the hill, just after the telescope was delivered; - The morning condensation ends up sticking it all on the mirror.... I followed the AstroSysteme PDF instructions for cleaning, with some additional details brought by the experience: Deionized water 2.5 l ; Isopropyl alcohol 1 l ; Take a few pictures, in order to compare FORWARD and AFTER, and in particular the side label that indicates the actual focal length measured by the mirror polisher. On one of these we can read diam = 298 mm, and focal length 1132 mm. Also locate the position of the mirror in relation to its holding cage, so as not to have to touch the adjustments of the six nylon side screws; This 300 mm mirror was completely dismantled and placed on the terrace table on a slope; The weather was sunny, but the wind gusted up as soon as the mirror got wet (so you have to look at the weather beforehand); The first operation is to clean the back of the mirror, and its edge, so that this dirt does not then come back to dirty the front face; you had to live it to understand it When spraying the mirror with water and Teepol, soak, then wait 5 minutes for everything to soften, then water again and observe the water flowing down the mirror. At first it is quite "loaded", then the water becomes transparent again with just many bubbles It is then time to start putting down sheets of absorbent paper by spraying a lot, wait, then take them off and throw them away. Rinse thoroughly, repeat. We must not try to remove all the defects, the improvement of the image would be infinitesimal, and the risks too severe on the other hand; therefore accept the imperfection; for me it was debris from the fire with tar that came to the telescope one week after the fire. I didn't touch it; maybe acetone would be better suited to dissolve tars? Then, the microfibre wipes needed to finish the job are so much prettier in all colours at Amazon. But in order to avoid a heart attack it is better to wash them (by hand) before use, so that they "bleed" their colour. Otherwise we see colored threads going through the mirror all clean. It is still necessary to soak the wipes before use. So do not use a washed but dry wipe, thinking that it will absorb more... possible scratches then, because the wipe is "stiff"; Finally, with absorbent paper, vacuum up the liquid isopropyl alcohol bead that accumulates by gravity in the bottom mirror. Just touch it on the edge of the mirror and it disappears immediately. It is never reassuring to see a liquid blade gradually evaporate, possibly leaving a mark. Put the mirror back in its cage. The three upper holding tabs are simply placed on the mirror, and held slightly with one finger of the hand while tightening its two screws. Before this procedure, the holding legs had a distance of 1 to 2 mm of clearance from the mirror, and the mirror made "Clong !" when it tipped with the mount. Now it's better.... As my explanation is translated with DeepL you can correct it in good English, and republish it here. If some people want to do it in Spanish it would be generous too:) Fabrice Bonus : Spanish telescope in Sierra Nevada used, with others in the world, to shot the first "black hole".

1 - deionized water + Teepol 2 - rinsing 3 - isopropyl alcohol

(es – NGC 2020) Esta nube está compuesta principalmente de gas, muchas estrellas jóvenes y estrellas en formación. NGC 2020 tiene una forma circular. La nube ha adoptado esta forma porque en su centro se está formando una estrella muy caliente. Su tonalidad azulada viene dada por la energía irradiada por la radiación de las nuevas estrellas que nacen en la nube. Esta energía separa los electrones de los átomos de oxígeno, dando a la nube su tinte azulado. (en – NGC 2020) This cloud is mainly composed of gas, many young stars and forming stars. NGC 2020 has a circular shape. The cloud has adopted this shape because in its center, a very hot star is forming. Its bluish hue is given by the energy radiated by the radiation of the new stars being born in the cloud. This energy detaches electrons from oxygen atoms, giving the cloud its bluish tint. --- Wikipedia --- https://commons.wikimedia.org/wiki/File:Two_very_different_glowing_gas_clouds_in_the_Large_Magellanic_Cloud.jpg?uselang=fr

Hi Mark, Congratulations! This target remains below the horizon all year round for me.... Too bad My eyes were drawn to the blue torus on the right: NGC 2020, then I looked for the explanation in Wikipedia. Fabrice

I really like the contrast between the light drapes (beshawles ?), as well as their delicateness, and the very black background. I still have a lot to learn. Muchas gracias. (DeepL translation )

(I dont't speak English - I use DeepL Translator ) Hi, Yesterday afternoon... 1/ I understand why my tube makes noise! The screws are tight, but the mirror moves 2 mm !!! I put foam on it. I collimate. Before, I had eccentricities that evolved from 0.37 to 0.88 from one image to another one! Tonight the standard deviation of the eccentricity values (PixInsight) decreases significantly : 0.58 -> 0.61. My images are still mediocre (Eccentricity > 0.45), but now they are all weak in the same way 2/ During the collimation I discover that the secondary mirror is corroded. (During nights I use QSI Camera, not my Canon Ixus pink ) In Andalusia the climate is dry, and the equipment is stored dry inside the house during the rainy season. This morning by looking carefully at the picture, the origin of the defect appears. I needed a night's sleep to understand the error during manufacture!!!!! And you, how long to understand? 3/ My next problem is to understand why I could never set the "PID" in RA during slewing. The mount rumbles, then stalls when it passes near the polar axis... During 50 sames images during a night, the pointing always drifts in RA, and the eccentricity increases with the duration of the photo. This should require another post… Hasta luego La Cebra de Andalucía

Hi, English is hard for me. Could we see image for each one ? La Cebra Here, I use DeepL translator