Talk:Virtual 3D Antenna Array Visualization Toolkit Project
From setiquest wiki
We can use this page for general project discussions.Jrseti 10:42, 12 May 2011 (PDT)
IRC discussion logs
- May 18th IRC chat log at http://irc.sigblips.com/setiQuest/2011/setiquest.05-18-2011.log
Have you considered using Google Earth as a platform for this visualisation project?
Liquid Galaxy Project Admin - User:18.104.22.168 01:47, 20 March 2011
- We are using Google Sky for a different part of the project. I did not realize that you can visualize external objects on Google Earth. Thanks for suggesting. We will take a look. - User:Avinash 09:57, 21 March 2011
- I investigate this. You can visualize external objects on Google Earth, but the capability is pretty limited. For instance you wouln not be able to 3D control the antennas very well.Jrseti 15:43, 19 May 2011 (PDT=
Thanks for the meeting yesterday (may 18, 2011)
You all need to get an account on http://issues.setiquest.org. There are issues we need to start with. Please volunteer by assigning yourself to an issue. Then discuss the items on this page.
- We need a project requirements document. Can several of you take on this? You can assign yourself to http://issues.setiquest.org/issues/293. Then start a discussion here on this page.
Since we're working with the iterative process, we don't need to write every part of the program all in one shot. I've been thinking about it, it seems like we could break it down like this:
- Landscape section
- Get the google elevation data, save it to a file
- Create a height map from that data
- Structure data (in our case, satellites)
- Define their position in a file by height relative to sea level, and GPS coordinates, and oritentation with respect to North.
- Define any animations, methods needed for the structure.
- GUI Data
- Show a feed on screen updated with any information related to the structures
- In our case, every time they changed position or their health changed, the structure object would notify the gui and the change would be displayed.
We could work on each section in small teams, writing driver functions where the tie-ins would exist to the other sections. That would give us working prototypes for the next iteration.
Sound good? --Rkenny
- Breaking it down into sections and working on them with small teams seems like a good idea; this would also foster 'peer review' of code. We must not forget requirements need to be more general, by general I want to emphasize on the toolkit's design so that it can even be used by other similar projects. --Atneik
- I'm not sure how we can make it more general while remaining in the scope of the project? What would improve it?--Rkenny
- We need several people to download JMonkey and try it out. Then document how it works so we all can try it. http://issues.setiquest.org/issues/292
Link to JMonkey page
- I've been playing around with JMonkey for a few days. I wrote out what I've found. I'm new to the Google API, though.--Rkenny 17:38, 20 May 2011 (PDT)
See http://setiquest.org/wiki/index.php/Development_JSON This should explain how to use JSON. Also, the Eclipse project https://github.com/setiQuest/3D-Antenna-Virtualization has some good JSON examples.
See http://setiquest.org/wiki/index.php/GitHub for the Git tutorial. You will need to practice to get used to Git.
Jrseti 12:27, 27 June 2011 (PDT) I created a start of an Eclipse project in the Git repository. See https://github.com/setiQuest/3D-Antenna-Virtualization. This provides running examples for unit testing (jUnit) and JSON (using jackson). I was able to fork and clone this project and bring it up in Eclipse and the unit tests work. This was a lot of work for me, Eclipse gave me a hard time setting up this project.
We can use this project for:
- The Eclipse project where our project will live.
- The example code shows how to properly add the required headers and javadoc comments.
- As mentioned in other documents, we will be programming with Unit testing. The examples shows how to do this.
- JSON will be used for process communication. There is a good example in the project that shows how to do it.
This is the Eclipse version I used:
Eclipse IDE for Java Developers Version: Helios Service Release 1 Build id: 20100917-0705 (c) Copyright Eclipse contributors and others 2000, 2010. All rights reserved. Visit http://eclipse.org/
You should use the same version. There are other versions and there can be differences that may cause frustration. Please use this version.
The Architecture document is ready for review. See Architecture document. Please review and ask questions. Or better yet, make changes yourself.
Detailed Design Document
The Detailed Design Document is ready for use to build upon. See Detailed Design Document.
There are 3 new issues created for completing the Detailed Design Document:
How We Should Proceed
We need to complete the Detailed Design Document first. This will take some work. This is where we all work together to design exactly what this will do, and how to do it.
Jrseti 16:54, 29 June 2011 (PDT) Today I added several more issues that may be a good place to start for those that are interested. See issues 221,222,223.