Please email any questions to [email protected].
- Download Unity (Personal Edition is fine).
- Download GitHub Desktop.
- On the 2dF repository page, select "Clone or download", "Open in Desktop", "Launch Application".
- Clone to your desired location.
- Replace the "2dF" in the project name with the name of the new survey.
- In the project, delete the contents of the "Data" folder.
- In Assets, rename "2dF Visualisation.unity" to "[Name of New Survey] Visualisation.unity".
- Delete "2dFLogo.png".
- Delete "2dFProcessed.txt" in Assets/Resources.
- Add the raw data for the new survey, e.g. in the form of a .txt file.
- Write a Python programme to convert the raw data to the table below, in a .txt file, with the values separated by commas in the format:
x position, y position, z position, Red, Green, Blue, Radius of particles
for each galaxy, with each galaxy separated by a new line.
Note that you may choose to keep some or all of the RGB values and and radius of the particles constant, and hence would not need to include this in the file
Output the data to Assets/Resources/[Name of New Survey]Processed.txt
For example, the programme to convert the 2dF data includes the line:
ascii.write(dataTable, "../Assets/Resources/2dFProcessed.txt", delimiter=",", format="no_header")
Run this programme to place the data in the required location.
While writing the programme, make a note of how many units in the Cartesian output correspond to 1 redshift unit. For example, for the 2dF survey, 1000 Cartesian output units correspond to 1 redshift unit.
- In Assets/Runtime Scripts/Scale Grid/CreateGrid.cs, set redshiftScale on line 7 to the value noted down previously.
- In the same script, set intervalLength on line 9 to the desired number of units in the Unity visualisation space between successive scale rings.
- In Assets/Resources/Constants.txt, replace the 300 with the outer limit in Unity visualisation space units that the camera can reach in any dimension from the origin, which also corresponds to the radius of the outer ring of the scale grid (you can decided on this by playing around in Unity). Note that you may wish to override this in the script to draw the scale grid to prevent confusion with a distance in ly greater than the age of the universe, see the CreateGrid.cs script in the WiggleZ repository for an example of when this has been the case.
- Also in CreateGrid.cs, you frustratingly must manually input the distance in Gly corresponding to each redshift, so write the code to do this in the format of lines 39-48. You can find the values for each redshift value using the calculator here.
- In Assets/Runtime Scripts/AddGalaxies.cs, for any colour values that are to remain constant for all galaxies set the values, e.g. 0.5f.
- For any colour values which are to vary between galaxies, set them from the required index in the text file containing the processed data.
For example, say the data contains the Cartesian coordinates, red values, and blue values. Each line would be in the format:
x, y, z, R, B
So the R value would be at index 3, hence set redValue = galaxyData [i][3], and blueValue = galaxyData [i][4] 15. If the particle size varies between galaxies, this can be set in a similar way to the colour.
- On line 22, remove the "=2f" part.
- Within the loop starting at line 52, add the line particleSize = galaxyData[i][x], where x is the index in a line in the processed data file that stores the radius of the particles. Ensure this is before line 57.
- Change "2dFProcessed" in line 30 to [Name of New Survey]Processed.
- In Assets/Runtime Scripts/, on line 13, change the speed that the camera flies around the survey if desired.
- Change the logo:
- Create the logo as a .png file and resize it to 512x512px. Place it in "Assets".
- In Unity, select "File", "Build Settings...", "Player Settings" and "Select" under "Default Icon" in the Inspector panel. Select the new logo. (To open the project in Unity, select "Open", navigate the the repository, and click "Open". To open the scene, in the "Project" window, navigate to Assets, and double-click "[Name of New Survey] Visualisation.unity".)
- In "Icon", next to the 192x192 option, select the same logo.
- Build the apk:
- Select "File", "Build Settings...".
- Under "Other Settings" in the Inspector panel, replace "TwodFSurvey" in the bundle identifier with the name of the new survey.
- If you plan on submitting an update to Google Play, increment the Version and the Bundle Version Code by 1.
- FOR THE FIRST TIME ONLY under "Publishing Settings", create a new keystore. Remember the password (for all of the projects so far it is "survey"). IF YOU CREATE A NEW KEYSTORE ONCE IT'S BEEN SUBMITTED TO GOOGLE PLAY, YOU WILL NOT BE ABLE TO SUBMIT A NEW UPDATE so always "Use Existing Keystore" after publishing.
- Upload the new project to GitHub:
- In Unity, select "Edit", "Project Settings", "Editor".
- Ensure the version control mode is set to "Visible Meta Files".
- Ensure the Asset Serialisation is set to "Force Text".
- On the GitHub website, create a new repository named "Cardboard-Universe-[Name of New Survey]
- Add the .gitignore Unity template.
- Once the repository is created, clone it to the GitHub desktop like when this was downloaded.
- Open up the project in Finder.
- Copy and paste the Assets, Project Settings, and Data folders to the newly-created local repository.
- Click the icon in to top-right-hand corner in GitHub desktop to change to the local respository.
- Commit the changes to master.
- Select "Sync" to upload the new project to GitHub.
- Add this README file to the repository.
I'm pretty sure this is complete, though I have most likely missed out some minor steps along the way so feel free to email me with any questions if you run into problems.
The Google VR SDK for Unity, which contains the required scripts and prefabs, such as the camera.
Stores any custom-made materials, e.g. the material of the galaxy particles.
Contains any plugins that extend Unity's features. I haven't added any, but I deleted the iOS one because there was a file that was greater than GitHub's 100 MB limit.
Contains any files that are to be accessed by the runtimes scripts.
Contains the data that has been processed and is ready to be accessed by AddGalaxies.cs. Contains x, y, z coordinates, possible R, G, B values, and possibly the radius of each galaxy.
Stores any constants that are to be accessed by more than one script. Currently only contains the outer boundary of the visualisation in Unity units in each dimension, used to determine when to stop the camera if it moves too far from the origin and the radius of the outer scale ring.
Contains C# scripts to be run during runtime. Note that they must be attached to (often empty) game objects to be run automatically. The lines within the Start() function are run when the app opens, while those within the Update() function are called once per frame. See the comments for detailed information about each script.
Takes information from the processed data .txt file about e.g. galaxy position, colour, and size, and places the particles in space. Attached to the game object "SpawnGalaxies".
Controls the double-click-to-exit feature. Attached to the game object "Exit".
Controls the clicking to start/stop moving the gamera. Attached to the game object "GvrMain" (the camera).
For drawing the scale circles and text. Attached to the game object "SpawnGrid".
For actually drawing the circle. Called by CreateGrid.cs, so not attached to any game object.
The scene file.
The app's logo.
Stores information about the project settings. Unity generates these files; they do not need to be modified manually.
When uploading a Unity project to GitHub, generally only the "Assets" and "Project Settings" folders need to be uploaded as Unity generates the rest, but I have included the third folder "Data" which contains the raw data and a programme to process it.
This various a lot between surveys, so requires a Python programme to transfer it to the required format.
Converts the raw data to the required format as previously specified and adds to to the folder Assets/Resources/. See the existing repositories for examples of such data conversion.