The idealized tool Visionare was sketched up to be a visualization tool to aid specialists in the source-hunting tasks. That means that it would make the life of people going through missions' data, to find the same source among different datasets, so that one is able to compare different observations of the same target. In this way, the tool comes as a facilitator and a first step for finding celestial objects through different missions/catalogs.
In order to achieve that, a dynamic 3D sky map was thought to be the visual interface a user would rely upon to find his/her interests. In this sphere, the dots rendered on it surface would represent the actual source using the right ascension and declination measures. The user would also be able to see: time of start of exposure, time of end of exposure, name, instrument name of the observatory (if provided), observation ID.
A multilayer visualization would be accomplished by a set of filters, that would display different catalogs. The navegation itself through the sky map is to happen through mouse dragging on the sphere or button controlled.
The hope was to achieve a useful solution for specialists at NASA who may feel overwhelmed by massive amount of data and with a hard time trying to find sources on different catalogs.
In order correlate the differente catalogs/datasets, and with the advice of the experts from the chat, the 'name' field for each source would be used to intersect datasets and form the multilayered visualization.
Further futures could be implemented if time permitted, like providing a constructed Sky View URL for seeing the source appearance. An animated visualization based on time would be also added if possible. Finally, colors would also be added to the visualization as an extra feature.
Since I am the only member of this team and its creator, it is pretty straightfoward and personal the motivation behind this endeavour. I always liked astronomy since I was a little kid and I read books about it, both for the open public and more advanced ones, too. My field of occupation is Computer Science, a formal degree obtained years ago. Since I got out of college, I had the opportunity to work in a Synchrotron accelerator which boosted my passion for the Natural Sciences, specifically Physics. Nonetheless, I engaged advance level studies in Data Science and Big Data recently and I am also learning about Visualization and Story Telling in this program. It came to my knowledge the hackathon event by the same university I am studying. I never participated in a Hackathon before, and because all of my background and interests I thought it to be a good experience, which was indeed. Finally, I chose the Observe category and found this challenge. It was very similar to a research project proposal I once did, which would use neural networks in order to classify large astronomical datasets in one of the two categories: star or galaxy. Since I elaborated this proposal, I was aware of the existence of Virtual Observatories and the scientific effort of providing ease access to unexplored huge datasets.
Unfortunately, I faced two problems in the development of the project. One of them was the data pipeline I created was broken for some bug that is happening with Tableau Prep (the version I used is listed below). I searched the web for the occurrence of the problem, and indeed, there are other people experimenting this too. The software gets in a eternal loop for "validating flux and generating schema" at some point of one's data transformations. What I was doing was to load and organize/clean columns associated with name, right ascension, declination, start time for exposure, end time for exposure, observation ID, instrument name from the following datasets:
Tipically, at the point of having all of these datasets inserted in an ETL flux in Tableau Prep, the transformation of cleaning entries with right ascesion and/or declination fields being null would get me stucked at the cited problem. I hoped that Tableau would be stable and reliable, but in the end it blocked the development of the solution right at the pre-stages of the project, which is disappointing.
The second problem which occured before the one above, got me precious hours overnight of October 3rd-4th. I was trying to find a sphere model, converting it to an acceptable format in Tableau Desktop (from .stl to .tde) and loading the converted file. The first model I found was had a non-readable file (ascii), so I could not convert it at all. I then found one that was convertible, but conversion seemed to whipe out some chuncks of data. Besides, getting access to a converting tool took me time, also.The references I used did not provide any sphere model. Furthermore, the calculated rotation measures from the workbook³ were all null values. I followed the steps in the tutorials cited, but I was facing a total different scenario of inadequacy. During all of this time, I was chatting with experts/ambassadors/moderators and I formally thank their help which showed me possible workarounds many times. In the afternoon of October 4th I decided to simplify the project in order to make it viable, so I decided with the advice from NASA experts, to project right ascension and declination in a 2D image of the sky. That's when I went over to Tableau Prep and got stucked. This lead me to the conclusion I wouldn't get any further with more attempts. Substituting Tableau Prep was not an option, I did not have time. Dead end. I understood it was time to stop and accept the state of the situation and start writing the Project for submission.
The original idea was to publish the 3D sky map in Tableau Public server, so anyone could use the tool.
Below I list down all the resources used:
Software
Hardware
Addiotionally I wrote a documentation right at the hackathon start that I provide below:
Create a VISUALIZATION TOOL that can help people interested in EXTREMELY ENERGETIC COSMIC PHENOMENA to access the data quickly and easily.
I used mainly HEASARC Browse (<https://heasarc.gsfc.nasa.gov/db-perl/W3Browse/w3catindex.pl>) web interface for looking for datasets and finding missions/catalogs. Issueing queries there I was able to generate text files that were then loaded in the ETL tool.
The catalogs/dataset used were (all Observation table types):
The reason for using the Observation table types is that, after consulting experts in the chat, it provides all the information a user would be interested to see in this tool and to identify the same source in different catalogs. In other words, answering what and when was imaged, with the use of the name and coordinates, for what, and exposure time interval, for when.
Unfornately, there is no solution to be shown due to reasons explained above.
1.Flerlage, Ken. "Creating a 3D Star Map in Tableau". January 20, 2018. Source:
<www.flerlagetwins.com/2018/01/creating-3d-star-map-in-tableau_55.html>. Visited on
October 3rd, 2020.
2.A'Hearn, Anya. "The 3D Tableau Full Monty". November 30, 2016. Source:
<https://www.datablick.com/blog/2016/11/22/the-3d-tableau-full-monty>. Visited on October
4th, 2020.
3.Beran, Bora. "Going 3D with Tableau. December 18, 2015. Source:<https://public.tableau.com
/views/3DChartsinTablea
/Simple3DScatterplot?:embed=y&:display_count=no&:showVizHome=no>. Visited on October
4th, 2020.
4. Riggs, Philip D. Package for converting STL files to TDE. Source: <https://gallery.alteryx.com/#!app/Convert-STL-to-TDE/583e52c8f499c70468980488>. Visited on October 4th, 2020.
5. Sphere model from Wikimedia. Source: <https://commons.wikimedia.org/wiki/File:3d_model_of_Sphere.stl#file>. Visited on October 4th, 2020.
6. Burkardt, John. Sphere model from Florida State University: <https://people.sc.fsu.edu/~jburkardt/data/stla/stla.html>. Visited on October 4th, 2020.