alix

Alix

for this project, the purpose is to connect alix to taphandle and for each table who have position coordonnate in taphandle, give the possibility to show a button who can launch alix and when alix is launched, we can use it to get order position of table in taphandle.

1-connect alix to taphandle: done!

2-show a button who can launch alix every single table who have position coordonnate: done!

3-Loading the firt position of every single table who has position coordonnate : done !

4-Display the positions of a table containing coordinates taphandle position on alix and at each move on alix, display the new coordinates the modified file is in Alix project>webcomponent>demo>alixTproReady.js: done!

To do this, we have used curl to verfied and get the correct url by typind in the terminal :

curl --head -X POST 'http://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/tap/sync?RUNID=TapHandle-betacadc;ivoa;ObsCore&PHASE=RUN&REQUEST=doQuery&LANG=ADQL&QUERY=SELECT++TOP+100++*%0AFROM+ivoa.ObsCore%0A'

5- Modified the Alix API file to give the possibility to enter a URL and the name of a table to display on alix the positions of this table. : done !

To do this we created a file alixCACDReady.js in alix and we loaded this file in alixapi.html.

** # difficulties encountered**

Difficulties to Remouve the button when we want load somme table who doesn't have position coordonnate: in progress! Difficulties to display the button only once when loading different tables that have position coordinates: in progress!

Some Bugs have been encountered when loading some tables in tabhandle, especially the XMM ObsCore10 table. The 64 base is not yet implement in gavo an simbad database so we can't display their position table in alix app. we have just displaying a message to sho user that the services is not yet implement went cliking on each table.

**# solution found **

Display the button beford the end of title of every component that have table who has position coordonnate: done! the modified files are in taphandle project>webcomponent>javascript>resultpaneView.js

////////////////////////////////////////////// à partir 29/09 ///////////////////////////////////////////

For this day the goal was to create a singleton object that would take into account all the actions previously implemented in AlixApiReady and then each time we want to execute an action, call a function of this object to execute the action in question, which was done by the singleton alixApi name. In fact, alixapi is an object that gathers all the functions necessary for the execution of an action on Alix such as for example the display of the results of a query made on a table of one of the TabHandle databases on the Alix interface. The different tests performed were made on the 3XMMDR8 and CACD databases. And so after these tests worked, we updated the Alix home page, especially the demo.js page to show the users the new way to configure Alix and the examples of queries to make.

The connection between the newly designed api has also been made with the TabHandle application but still, problems still persist when we try to reload the masterRessource. These problems are currently being checked and progressively corrected. The solution to the masterRessource problem has been found so we can now display the results of our tables on taphandle. Functions such as ## shopPopupData and ## initializeData have been developed in our new AlixApi file to solve the problem.

We try to make a synchronization between the alix load button and the ones located in the table(done)

So we try to generalize this solution by using the information contained in the paring nodekey for each database!(done)

We also decided to make a display of the region. The problem that arose here was the different points that constitute a region, for example on 3XMM for example, where the regions are defined by only two points and therefore the result obtained here is just a straight line, however our tests were done on cacd which has many more points to define a region. We managed to highlight the region but there is still a problem at the default zoom level. This will allow us to have a clearer and more precise visual aspect of the defined region.

The Test can currently be done on any database because a function has been written << testFigure >> which allows us to check the number of points (coordinates contained in our coordinate table) and returns the type of figure in question.

The default zoom problem has also been solved by modifying the setRefferenceView function in the AladinLite_v file. By calculating the default size of our alix screen, we return the zoom which is fine.

we can now draw and or delete regions. to do this we have created a <> function in aladinLite_v which we call in the <> function of alixApi in order to delete our regions.

               Problems encountered:

Problems have been encountered when testing the SIMBAD and GAVO databases for example and the major source of these problems is due to the fact that these databases are encoded in base 64 from where the result provided is a result that remains to be processed. For the moment we are trying to pass a parameter such as the format=votable/td in the url of our request to see if we get a satisfactory result because this parameter is the one that will allow us to convert the result obtained in order to be able to display it on Alix.

the second thing was to clean up and comment the code add and update the alix html page which was also done