The 200" Hale Telescope on Mt. Palomar
-
Topic authorselden
- Developer
- Posts: 10192
- Joined: 04.09.2002
- With us: 22 years 2 months
- Location: NY, USA
V2 of the Hale Telescope Addon is now available.
It requires Celestia v1.5.0 pre4 or later.
http://www.lepp.cornell.edu/~seb/celest ... ope_v2.zip
(10.4MB, expands to 51MB).
[edit]
Sorry: I forgot to mention the new features. which are why v2 is so much larger than v1.
0. The resolution of the model is significantly increased.
1. The Hale Telescope model points toward whatever object is selected.
2. Manual control of various components of the telescope and of the observatory is available.
3. 3D labels of many of the telescope's parts can be turned on and off.
4. It demonstrates the improvement in resolution provided by the adaptive optics.
5. It shows the paths taken by light in the 5 different observation configurations (only 3 of which are still used).
I've probably forgotten something...
[/edit]
It requires Celestia v1.5.0 pre4 or later.
http://www.lepp.cornell.edu/~seb/celest ... ope_v2.zip
(10.4MB, expands to 51MB).
[edit]
Sorry: I forgot to mention the new features. which are why v2 is so much larger than v1.
0. The resolution of the model is significantly increased.
1. The Hale Telescope model points toward whatever object is selected.
2. Manual control of various components of the telescope and of the observatory is available.
3. 3D labels of many of the telescope's parts can be turned on and off.
4. It demonstrates the improvement in resolution provided by the adaptive optics.
5. It shows the paths taken by light in the 5 different observation configurations (only 3 of which are still used).
I've probably forgotten something...
[/edit]
Selden
-
Topic authorselden
- Developer
- Posts: 10192
- Joined: 04.09.2002
- With us: 22 years 2 months
- Location: NY, USA
A teaser for the next version:
I'm starting to implement the telescope's control desk.
It's no longer in use for the real telescope since everything is computer controlled, but I thought it'd be fun to simulate it in Celestia.
This shows a trial version, implementing buttons for some of the features of the Addon that are unavailable in real life
.
Clicking on one of the buttons in the vertical column hides the specified element of the model. The horizontal rows of buttons implement "radio buttons" -- when one is selected (and lights up green), the others in that row turn off (lighting up blue). They're all 3D: they go down when they turn on and pop back up when turned off.
I'm starting to implement the telescope's control desk.
It's no longer in use for the real telescope since everything is computer controlled, but I thought it'd be fun to simulate it in Celestia.
This shows a trial version, implementing buttons for some of the features of the Addon that are unavailable in real life
.
Clicking on one of the buttons in the vertical column hides the specified element of the model. The horizontal rows of buttons implement "radio buttons" -- when one is selected (and lights up green), the others in that row turn off (lighting up blue). They're all 3D: they go down when they turn on and pop back up when turned off.
Selden
-
- Posts: 835
- Joined: 27.09.2004
- With us: 20 years 1 month
- Location: Massachusetts, USA
-
- Developer
- Posts: 3776
- Joined: 04.02.2005
- With us: 19 years 9 months
- Hungry4info
- Posts: 1133
- Joined: 11.09.2005
- With us: 19 years 2 months
- Location: Indiana, United States
-
Topic authorselden
- Developer
- Posts: 10192
- Joined: 04.09.2002
- With us: 22 years 2 months
- Location: NY, USA
Re: The 200" Hale Telescope on Mt. Palomar
In case anyone might be interested....
More to play with blogging than anything else, I'll occasionally put some updates on the progress of the next version of the Hale Telescope Addon at
http://celestiaguru.blogspot.com/
More to play with blogging than anything else, I'll occasionally put some updates on the progress of the next version of the Hale Telescope Addon at
http://celestiaguru.blogspot.com/
Selden
-
- Developer
- Posts: 3776
- Joined: 04.02.2005
- With us: 19 years 9 months
Re:
selden wrote:Another teaser for the next version:
This shows an early version of the official control desk...
Huh... I miss this! Nice!!
Re: The 200" Hale Telescope on Mt. Palomar
Selden, great work. I love this controlling of movement in Celestia. I love any animating features .
Is something like this also possible as automated feature. Can one control a body movement in Celestia from outside? For example via lua hook script or a scripted function?
For example is there a way to tell the telescope to open the doors when a specific event is happening? Space Shuttle opening a door? A s/c that has to draw aside to not crash into another s/c or space debris?
For example by reading/ controlling from a file or socket?
Thanks
Stuffer
Is something like this also possible as automated feature. Can one control a body movement in Celestia from outside? For example via lua hook script or a scripted function?
For example is there a way to tell the telescope to open the doors when a specific event is happening? Space Shuttle opening a door? A s/c that has to draw aside to not crash into another s/c or space debris?
For example by reading/ controlling from a file or socket?
Thanks
Stuffer
Win XP Pro x Core2Duo 2,1GHz x 2 GB RAM x NVidia Quadro FX 1500 256 MB
-
Topic authorselden
- Developer
- Posts: 10192
- Joined: 04.09.2002
- With us: 22 years 2 months
- Location: NY, USA
Re: The 200" Hale Telescope on Mt. Palomar
Stuffer,
The telescope components are controlled by ScriptedOrbit and ScriptedRotation functions.
Commands are passed to those functions by Selecting an appropriately named DSC object. (It won't stay selected. Whenever it recognizes a command, the command recognition function immediately re-selects the previously selected object.)
You might take a look at the script show_lightpaths.cel
It demonstrates control of the model.
You could write a CelX script to watch for whatever events you want and then invoke appropriate telescope commands.
Most of the movements in the telescope model take 10 seconds to finish, so I wouldn't have to provide "motion has completed" status functions.
Maybe next version.
The telescope components are controlled by ScriptedOrbit and ScriptedRotation functions.
Commands are passed to those functions by Selecting an appropriately named DSC object. (It won't stay selected. Whenever it recognizes a command, the command recognition function immediately re-selects the previously selected object.)
You might take a look at the script show_lightpaths.cel
It demonstrates control of the model.
You could write a CelX script to watch for whatever events you want and then invoke appropriate telescope commands.
Most of the movements in the telescope model take 10 seconds to finish, so I wouldn't have to provide "motion has completed" status functions.
Maybe next version.
Selden
Re: The 200" Hale Telescope on Mt. Palomar
Just wonder how DEM file/data can be used or directly loaded into Celestia? I searched the Forum hoping to find out how to ultilise DEM file in Celestia's add-on, can anybody point me to the right direction for this?A model of the Hale Telescope on a DEM of Palomar Mountain and tracking Tau Ceti is available at
Joe
-
Topic authorselden
- Developer
- Posts: 10192
- Joined: 04.09.2002
- With us: 22 years 2 months
- Location: NY, USA
Re: The 200" Hale Telescope on Mt. Palomar
Unfortunately, Celestia does not have the capability of using DEM data directly.
I used 3DEM to translate the DEM into height data, and wrote my own program to translate the height data into Celestia's CMOD model format. Aligning the bumps with the topo map was a pain -- a lot of trial and error. Mostly error.
I used 3DEM to translate the DEM into height data, and wrote my own program to translate the height data into Celestia's CMOD model format. Aligning the bumps with the topo map was a pain -- a lot of trial and error. Mostly error.
Selden
Re: The 200" Hale Telescope on Mt. Palomar
Thanks Selden, that was certainly a very delight confirmation for me as I was using a similar approach to using DEM data in Celestia. What was frustrating is to fix the final CMOD onto the face of a planet. No matter how many trials, always (never even mostly) errors. Is there a better way than CMOD in resolving the trial-and-error approach?
Joe
-
Topic authorselden
- Developer
- Posts: 10192
- Joined: 04.09.2002
- With us: 22 years 2 months
- Location: NY, USA
Re: The 200" Hale Telescope on Mt. Palomar
Joe wrote:Thanks Selden, that was certainly a very delight confirmation for me as I was using a similar approach to using DEM data in Celestia. What was frustrating is to fix the final CMOD onto the face of a planet. No matter how many trials, always (never even mostly) errors. Is there a better way than CMOD in resolving the trial-and-error approach?
I'm not sure what you're tying to say.
The SSC coordinate system declarations available in Celestia v1.6.0 and later can make placement of a model on a planet's surface relatively easy.
If its edges are exactly on north-south and east-west directions, placing a model in the correct position on the surface of a planet, with the correct orientation and size, should require only some relatively straight-forward arithmetic if you know the latitude and longitude of the center of the model (or one of its corners) and its dimensions. (I'm assuming that the model is small relative to the curvature of the Earth's surface. Otherwise there are mapping coordinate system effects that you may need to take into account.)
If you can't be sure of some of these prerequisites, then some way to change and measure an object's position and orientation in real-time is needed, which Celestia doesn't provide.
For example, here's the SSC placement code that I used for my VLA model. I split the placement code into two objects because of the way I structured the models. I've added some explanatory comments.
Code: Select all
# SurfaceObjects are "correctly" oriented perpendicular to the local surface of the planet
SurfaceObject "vla-00" "Sol/Earth"
{
# this object is just used for reference, so it doesn't need to be visible
# except while testing
Class "invisible"
#the actual Radius value doesn't matter, since this object is not visible
# if it's too small, though, the object won't be drawn and objects referencing it won't be drawn, either.
Radius 0.0125
# specify longitude (+ values are East of the prime meridian),
# latitude, and altitude (in km above sealevel)
FixedPosition { Planetographic [ -107.6177275 34.0787492 2.124]}
FixedRotation { }
}
# below is the definition of the pedestal supporting the VLA telescope's yoke
# the Path used in its name doesn't need to include the reference object above
# because that is specified in the Frame declarations.
# This Name and Path determine where this object is listed in Celestia's
# Navigation/Solar System Browser menu
"vla-00-base" "Sol/Earth"
{
Class "component" # avoids having to specify Albedo so it doesn't glow
Mesh "vla-base.cmod"
# The Radius (in km) must enclose this object's mesh so the object will be drawn correctly
# but does not itself determine the size of this object
Radius 0.0125
# Don't scale the Mesh to Radius. Instead use the model's internal dimensions.
# The object will be placed in Celestia relative to the center of the Mesh's internal coordinate system.
# In other words, if the object is offset relative to the coordinate system used by the software which created it, it'll be offset relative to the position used by Celestia.
NormalizeMesh false
# Scale the model's internal dimensions to km.
# The resulting object must be smaller than the Radius specified above.
# Otherwise only parts of it will be drawn from some viewpoints.
MeshScale 0.000055
# position the Mesh relative to the reference object
OrbitFrame { BodyFixed { Center "Sol/Earth/vla-00"}}
FixedPosition [ 0 0 0 ]
# orient the Mesh relative to the reference object
BodyFrame { BodyFixed { Center "Sol/Earth/vla-00"}}
FixedRotation {}
}
I hope this helps a little.
(My problem with the Hale telescope's ground surface texture was that topo maps have an arbitrary border and size, making it difficult to determine what values to use to cut out the correct small region corresponding to the mesh. Of course, there's also the issue of needing to know the exact coordinate system that was used for drawing the topo map in order to reproject a section of it correctly onto a slightly differently oriented flat object. I ignored that, since the error should have been relatively small.)
Selden
Re: The 200" Hale Telescope on Mt. Palomar
A big thank U to Selden, I got it done. It needs a lot of fine tuning and patience
Joe