{"action":"created","issue":{"url":"https://api.github.com/repos/PixInsight/PCL/issues/30","repository_url":"https://api.github.com/repos/PixInsight/PCL","labels_url":"https://api.github.com/repos/PixInsight/PCL/issues/30/labels{/name}","comments_url":"https://api.github.com/repos/PixInsight/PCL/issues/30/comments","events_url":"https://api.github.com/repos/PixInsight/PCL/issues/30/events","html_url":"https://github.com/PixInsight/PCL/issues/30","id":160884133,"number":30,"title":"INDIClient version 1.0.14.193","user":{"login":"jconejero","id":9529604,"avatar_url":"https://avatars.githubusercontent.com/u/9529604?v=3","gravatar_id":"","url":"https://api.github.com/users/jconejero","html_url":"https://github.com/jconejero","followers_url":"https://api.github.com/users/jconejero/followers","following_url":"https://api.github.com/users/jconejero/following{/other_user}","gists_url":"https://api.github.com/users/jconejero/gists{/gist_id}","starred_url":"https://api.github.com/users/jconejero/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jconejero/subscriptions","organizations_url":"https://api.github.com/users/jconejero/orgs","repos_url":"https://api.github.com/users/jconejero/repos","events_url":"https://api.github.com/users/jconejero/events{/privacy}","received_events_url":"https://api.github.com/users/jconejero/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-06-17T13:08:25Z","updated_at":"2016-06-21T16:43:06Z","closed_at":null,"body":"I've just committed a new version of the INDIClient module with many of the features we were discussing in other posts (apparent positions, better management of image properties/keywords, etc).\r\n\r\nLots of things to comment. I'll return here later with a description of changes.\r\n\r\nIMO this version is now 100% ready for release. Let's see how it performs under the real sky..."},"comment":{"url":"https://api.github.com/repos/PixInsight/PCL/issues/comments/227499182","html_url":"https://github.com/PixInsight/PCL/issues/30#issuecomment-227499182","issue_url":"https://api.github.com/repos/PixInsight/PCL/issues/30","id":227499182,"user":{"login":"vicentperis","id":18697387,"avatar_url":"https://avatars.githubusercontent.com/u/18697387?v=3","gravatar_id":"","url":"https://api.github.com/users/vicentperis","html_url":"https://github.com/vicentperis","followers_url":"https://api.github.com/users/vicentperis/followers","following_url":"https://api.github.com/users/vicentperis/following{/other_user}","gists_url":"https://api.github.com/users/vicentperis/gists{/gist_id}","starred_url":"https://api.github.com/users/vicentperis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vicentperis/subscriptions","organizations_url":"https://api.github.com/users/vicentperis/orgs","repos_url":"https://api.github.com/users/vicentperis/repos","events_url":"https://api.github.com/users/vicentperis/events{/privacy}","received_events_url":"https://api.github.com/users/vicentperis/received_events","type":"User","site_admin":false},"created_at":"2016-06-21T16:43:06Z","updated_at":"2016-06-21T16:43:06Z","body":"Hi,\n\nCongratulations on the new tool. You have some interesting comments by \nMike Schuster on the PI Forum. The things about the meridian flip can be \ntricky because some mounts handle the meridian flip automatically... \nAnyway, for all these options and the pointing model I think what we \nreally need now is some preferences about the observatory. Would it be \npossible to add in the EDIT menu an \"Observatory preferences\" option?\n\nRegarding the pointing model, I was talking with Juan about the numeric \napproach to the pointing model. Think also that this can be very useful \nto split the model in two parts (W and E) for GEMs. I'm thinking about a \ntool, not a script. In this tool, you can add files. Those files are \nimages that you previously acquired, so the pointing model is calculated \nby solving all the images and calculating the positional error. Then, \nalternatively, we have a kind of \"real time pointing model generation\", \nwhere you don't load any image and the scope starts to slew and acquire \nimages; after all the images are acquired, the images are solved and the \npointing model is generated.\n\nThen we should think how we can handle the calculated pointing model. \nIt's saved into a process icon? It's saved to a text file? Is it loaded \ninto the observatory preferences? It can be also useful to have multiple \npointing models available (in case you have a piggyback telescope with a \nsecond camera); in that case, it could be useful to use icons to load \nthe pointing model you'll be using that night.\n\nI'll be at the observatory from June 22nd to July 1st. I'll go there \nagain by the end of July. I can test it with a Paramount and a Meade 16\" \nOTA, and an Astelco mount with a Planewave 20\" CDK. Take into account \nthat I'll be at the observatory also by the en of August, but I'll be on \nholidays during September.\n\n\nV.\n\n\n\n\n\nOn 06/21/2016 05:31 PM, Juan Conejero wrote:\n>\n> Hi Klaus,\n>\n> Thanks! That paper is very interesting. See also a nice general \n> description of the pointing problem by the author of TPoint:\n>\n> http://www.tpointsw.uk/pointing.htm\n>\n> The project to implement a pointing modelling tool arises directly \n> from your idea of differential correction in INDIMount::ExecuteOn(). \n> The mechanics of building a pointing model are essentially the same: \n> compute differences between observation pointing locations and true \n> astrometrically solved positions.\n>\n> An analytical model is very nice, mainly because it attempts to \n> describe the causes of pointing errors, so it is also a diagnostics \n> tool. However, I am thinking more on a purely numerical solution, \n> which provides less information about mechanical issues but is IMO \n> potentially more accurate and flexible. Basically, we can build an \n> approximating surface spline (aka thin plate) from measured \n> differences in horizontal coordinates, then apply the spline to \n> compute corrections each time we send new coordinates to the \n> telescope. This is an /empirical pointing model/. It works exactly the \n> same way as in DBE to build a model of the image background, or in \n> DynamicAlignment to build an image registration model, for example. I \n> use surface splines also in StarAlignment to build local distortion \n> models. The big advantage of surface splines is that they are \n> extremely flexible, and hence able to adapt to extremely complex \n> functions. They are also numerically and computationally efficient, \n> especially as I use them in StarAlignment.\n>\n> The whole process of pointing model construction can be fully \n> automated, even using a relatively simple script, with INDICCDFrame \n> and INDIMount. This could be done right now, in fact. However, we need \n> several improvements, especially to include atmospheric refraction in \n> our apparent coordinate reduction model. We should have also \n> topocentric coordinates to be rigorous. This is the basic idea. Note \n> that it does not exclude the possibility to generate analytical \n> models, as described in the paper you've found. I think we should \n> explore both ways.\n>\n>     Looks not so complicated, but it will be difficult to test ...\n>\n> That's very true. Hopefully we'll be able to use some telescopes from \n> our university's observatory. Am I right, Vicent?\n>\n> —\n> You are receiving this because you are subscribed to this thread.\n> Reply to this email directly, view it on GitHub \n> <https://github.com/PixInsight/PCL/issues/30#issuecomment-227478009>, \n> or mute the thread \n> <https://github.com/notifications/unsubscribe/AR1Mqw9ivglwoXT1Tu4MkeeYOsXZ6qSVks5qOAPZgaJpZM4I4Vy8>.\n>\n\n\n-- \n****************************************************\nVicent Peris Baixauli\n\nAstrofotógrafo\nObservatori Astronòmic - Universitat de València\n\nEdifici Instituts d'Investigació.\nC/ Catedrático José Beltrán, nº 2.\nE- 46980 Paterna (Valencia)Spain\nTel. +34 96 354 3819\n\nOAUV: http://observatori.uv.es\nAstrofoto: http://astrofoto.es\nDSA: http://astro-photographer.org\nPixInsight: http://pixinsight.com\n****************************************************\n\n"}}
{"actor":{"display_login":"vicentperis"}}