[Spice_discussion] RE: [Spice_announce] Geometry Engine
Crary, Frank
fcrary@swri.edu
Mon, 24 Feb 2003 09:54:50 -0600
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C2DC1D.10272B80
Content-Type: text/plain;
charset="iso-8859-1"
All of the geometric events in that list seem to involve three bodies (i.e.
angular separation between body 1 and body 2, as seen from a spacecraft.) I
think it would be very convenient for particles and fields instruments to
have simple, 2 body events (e.g. range between spacecraft and planet body
center less than X or planetocentric latitude of spacecraft greater than Y.)
Frank
-----Original Message-----
From: Diane Conner [mailto:Diane.Conner@jpl.nasa.gov]
Sent: Friday, February 21, 2003 12:19 PM
To: spice@dcs04.jpl.nasa.gov
Subject: Fwd: [Spice_announce] Geometry Engine
>Date: Wed, 19 Feb 2003 09:00:33 -0800
>From: Lee Elson <Lee.Elson@jpl.nasa.gov>
>Subject: [Spice_announce] Geometry Engine
>Sender: spice_announce-admin@naif.jpl.nasa.gov
>To: spice_discussion@naif.jpl.nasa.gov, spice_announce@naif.jpl.nasa.gov
>X-Accept-Language: en-us, en
>X-BeenThere: spice_announce@naif.jpl.nasa.gov
>X-Mailman-Version: 2.0.13
>List-Post: <mailto:spice_announce@naif.jpl.nasa.gov>
>List-Subscribe: <http://naif.jpl.nasa.gov/mailman/listinfo/spice_announce>,
> <mailto:spice_announce-request@naif.jpl.nasa.gov?subject=subscribe>
>List-Unsubscribe:
<http://naif.jpl.nasa.gov/mailman/listinfo/spice_announce>,
>
<mailto:spice_announce-request@naif.jpl.nasa.gov?subject=unsubscribe>
>List-Archive: <http://naif.jpl.nasa.gov/pipermail/spice_announce/>
>List-Help: <mailto:spice_announce-request@naif.jpl.nasa.gov?subject=help>
>List-Id: General SPICE announcements <spice_announce.naif.jpl.nasa.gov>
>
>As part of an ongoing effort to increase the functionality of the
>SPICE Toolkit, we at NAIF are planning the development of SPICELIB
>routines that will allow the user to determine time windows or
>"schedules" when certain geometric constraints are met. To make this
>development process as efficient as possible, we'd like to determine
>which geometric constraints would offer the most "bang for the buck"
>in terms of useful functionality. Listed below are brief
>descriptions of what we've come up with (in a loose arrangement of
>decreasing priority):
>
>1)"Distance" -- determine time intervals during which the apparent
>distance between 2 specified bodies, as viewed from a specified
>observing body, satisfies a specified constraint (e.g. less than,
>equal to, greater than, between values)
>
>2)"Phase"-- determine time intervals during which the apparent
>observer-target-Sun angle satisfies a specified constraint.
>
>3)"Eclipse"-- determine time intervals during which one body is
>eclipsed by another as viewed by an observer.
>
>4)"Occultation/transit"-- determine time intervals during which one
>body is occulted/transited by another as viewed by an observer.
>
>5)"Time from periapsis/apoapsis"-- determine time intervals during
>which a body in orbit is within a specified time interval from
>periapsis/apoapsis.
>
>6)"Elevation"-- determine time intervals during which the elevation
>of an object, in a specified reference frame, satisfies a specified
>constraint.
>
>7)"Viewed Latitude/longitude"-- determine time intervals during
>which a viewed location (latitude/longitude) satisfies a specified
>constraint.
>
>8)"Nadir separation"-- determine time intervals during which the
>angle between an observed object and the nadir direction satisfies a
>specified constraint.
>
>9)"Separation"-- determine time intervals during which the angular
>separation of 2 bodies (as seen by an observer) satisfies a
>specified constraint.
>
>10)"Incidence/emission/solar longitude"-- determine time intervals
>during which the incidence/emission/solar longitude angle satisfies
>a specified constraint.
>
>11)"Orbital longitude"-- determine time intervals during which the
>orbital longitude of an object, relative to an observer, satisfies a
>specified constraint.
>
>12)"Angular velocity"-- determine time intervals during which the
>angular velocity of one object relative to another satisfies a
>specified constraint.
>
>13)"Apparent diameter"-- determine time intervals during which the
>apparent diameter of a body satisfies a specified constraint.
>
>14)"Elongation"-- determine time intervals during which the
>elongation (angular separation of a body from the sun) of a body
>satisfies a specified constraint.
>
>15)"Relative velocity"-- determine time intervals during which the
>velocity of one body relative to another satisfies a specified
>constraint.
>
>16) "User supplied"-- determine time intervals during which a
>function provided by the user satisfies a specified constraint.
>
>In addition to the time oriented "windows/schedules" discussed
>above, it is possible (but more work) to have other solutions. An
>example might be to find a range of viewed latitudes and longitudes
>for a specified time window.
>
>The main purpose of this note is to solicit your input. Are the 16
>constraints listed above of any use to you? Are there others that
>would be more useful?
>
>Regards,
>Lee Elson
>Lee.Elson@jpl.nasa.gov
>818-354-4223
>
>
>
>_______________________________________________
>Spice_announce mailing list
>Spice_announce@naif.jpl.nasa.gov
>http://naif.jpl.nasa.gov/mailman/listinfo/spice_announce
--
Diane Conner
--------------------------------
1.818.354.8586 voice 1.818.393.4669 Fax
SPICE: https://cassini.jpl.nasa.gov/csos/io/spice/
SPICE FILES: ftp://naif.jpl.nasa.gov/pub/naif/CASSINI/kernels/
PDS Archive: https://cassini.jpl.nasa.gov/pds_archive
------_=_NextPart_001_01C2DC1D.10272B80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Spice_announce] Geometry Engine</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>All of the geometric events in that list seem to =
involve three bodies (i.e. angular separation between body 1 and body =
2, as seen from a spacecraft.) I think it would be very convenient for =
particles and fields instruments to have simple, 2 body events (e.g. =
range between spacecraft and planet body center less than X or =
planetocentric latitude of spacecraft greater than Y.)</FONT></P>
<P> =
=
=
=
=
=
=
=
=
=
<FONT SIZE=3D2>Frank</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Diane Conner [<A =
HREF=3D"mailto:Diane.Conner@jpl.nasa.gov">mailto:Diane.Conner@jpl.nasa.g=
ov</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, February 21, 2003 12:19 PM</FONT>
<BR><FONT SIZE=3D2>To: spice@dcs04.jpl.nasa.gov</FONT>
<BR><FONT SIZE=3D2>Subject: Fwd: [Spice_announce] Geometry =
Engine</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>>Date: Wed, 19 Feb 2003 09:00:33 -0800</FONT>
<BR><FONT SIZE=3D2>>From: Lee Elson =
<Lee.Elson@jpl.nasa.gov></FONT>
<BR><FONT SIZE=3D2>>Subject: [Spice_announce] Geometry Engine</FONT>
<BR><FONT SIZE=3D2>>Sender: =
spice_announce-admin@naif.jpl.nasa.gov</FONT>
<BR><FONT SIZE=3D2>>To: spice_discussion@naif.jpl.nasa.gov, =
spice_announce@naif.jpl.nasa.gov</FONT>
<BR><FONT SIZE=3D2>>X-Accept-Language: en-us, en</FONT>
<BR><FONT SIZE=3D2>>X-BeenThere: =
spice_announce@naif.jpl.nasa.gov</FONT>
<BR><FONT SIZE=3D2>>X-Mailman-Version: 2.0.13</FONT>
<BR><FONT SIZE=3D2>>List-Post: <<A =
HREF=3D"mailto:spice_announce@naif.jpl.nasa.gov">mailto:spice_announce@n=
aif.jpl.nasa.gov</A>></FONT>
<BR><FONT SIZE=3D2>>List-Subscribe: <<A =
HREF=3D"http://naif.jpl.nasa.gov/mailman/listinfo/spice_announce" =
TARGET=3D"_blank">http://naif.jpl.nasa.gov/mailman/listinfo/spice_announ=
ce</A>>,</FONT>
<BR><FONT SIZE=3D2>> <<A =
HREF=3D"mailto:spice_announce-request@naif.jpl.nasa.gov?subject=3Dsubscr=
ibe">mailto:spice_announce-request@naif.jpl.nasa.gov?subject=3Dsubscribe=
</A>></FONT>
<BR><FONT SIZE=3D2>>List-Unsubscribe: <<A =
HREF=3D"http://naif.jpl.nasa.gov/mailman/listinfo/spice_announce" =
TARGET=3D"_blank">http://naif.jpl.nasa.gov/mailman/listinfo/spice_announ=
ce</A>>,</FONT>
<BR><FONT SIZE=3D2>> <<A =
HREF=3D"mailto:spice_announce-request@naif.jpl.nasa.gov?subject=3Dunsubs=
cribe">mailto:spice_announce-request@naif.jpl.nasa.gov?subject=3Dunsubsc=
ribe</A>></FONT>
<BR><FONT SIZE=3D2>>List-Archive: <<A =
HREF=3D"http://naif.jpl.nasa.gov/pipermail/spice_announce/" =
TARGET=3D"_blank">http://naif.jpl.nasa.gov/pipermail/spice_announce/</A>=
></FONT>
<BR><FONT SIZE=3D2>>List-Help: <<A =
HREF=3D"mailto:spice_announce-request@naif.jpl.nasa.gov?subject=3Dhelp">=
mailto:spice_announce-request@naif.jpl.nasa.gov?subject=3Dhelp</A>></=
FONT>
<BR><FONT SIZE=3D2>>List-Id: General SPICE announcements =
<spice_announce.naif.jpl.nasa.gov></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>As part of an ongoing effort to increase the =
functionality of the </FONT>
<BR><FONT SIZE=3D2>>SPICE Toolkit, we at NAIF are planning the =
development of SPICELIB </FONT>
<BR><FONT SIZE=3D2>>routines that will allow the user to determine =
time windows or </FONT>
<BR><FONT SIZE=3D2>>"schedules" when certain geometric =
constraints are met. To make this </FONT>
<BR><FONT SIZE=3D2>>development process as efficient as possible, =
we'd like to determine </FONT>
<BR><FONT SIZE=3D2>>which geometric constraints would offer the most =
"bang for the buck" </FONT>
<BR><FONT SIZE=3D2>>in terms of useful functionality. Listed below =
are brief </FONT>
<BR><FONT SIZE=3D2>>descriptions of what we've come up with (in a =
loose arrangement of </FONT>
<BR><FONT SIZE=3D2>>decreasing priority):</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>1)"Distance" -- determine time =
intervals during which the apparent </FONT>
<BR><FONT SIZE=3D2>>distance between 2 specified bodies, as viewed =
from a specified </FONT>
<BR><FONT SIZE=3D2>>observing body, satisfies a specified constraint =
(e.g. less than, </FONT>
<BR><FONT SIZE=3D2>>equal to, greater than, between values)</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>2)"Phase"-- determine time intervals =
during which the apparent </FONT>
<BR><FONT SIZE=3D2>>observer-target-Sun angle satisfies a specified =
constraint.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>3)"Eclipse"-- determine time intervals =
during which one body is </FONT>
<BR><FONT SIZE=3D2>>eclipsed by another as viewed by an =
observer.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>4)"Occultation/transit"-- determine =
time intervals during which one </FONT>
<BR><FONT SIZE=3D2>>body is occulted/transited by another as viewed =
by an observer.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>5)"Time from periapsis/apoapsis"-- =
determine time intervals during </FONT>
<BR><FONT SIZE=3D2>>which a body in orbit is within a specified time =
interval from </FONT>
<BR><FONT SIZE=3D2>>periapsis/apoapsis.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>6)"Elevation"-- determine time =
intervals during which the elevation </FONT>
<BR><FONT SIZE=3D2>>of an object, in a specified reference frame, =
satisfies a specified </FONT>
<BR><FONT SIZE=3D2>>constraint.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>7)"Viewed Latitude/longitude"-- =
determine time intervals during </FONT>
<BR><FONT SIZE=3D2>>which a viewed location (latitude/longitude) =
satisfies a specified </FONT>
<BR><FONT SIZE=3D2>>constraint.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>8)"Nadir separation"-- determine time =
intervals during which the </FONT>
<BR><FONT SIZE=3D2>>angle between an observed object and the nadir =
direction satisfies a </FONT>
<BR><FONT SIZE=3D2>>specified constraint.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>9)"Separation"-- determine time =
intervals during which the angular </FONT>
<BR><FONT SIZE=3D2>>separation of 2 bodies (as seen by an observer) =
satisfies a </FONT>
<BR><FONT SIZE=3D2>>specified constraint.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>10)"Incidence/emission/solar =
longitude"-- determine time intervals </FONT>
<BR><FONT SIZE=3D2>>during which the incidence/emission/solar =
longitude angle satisfies </FONT>
<BR><FONT SIZE=3D2>>a specified constraint.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>11)"Orbital longitude"-- determine =
time intervals during which the </FONT>
<BR><FONT SIZE=3D2>>orbital longitude of an object, relative to an =
observer, satisfies a </FONT>
<BR><FONT SIZE=3D2>>specified constraint.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>12)"Angular velocity"-- determine time =
intervals during which the </FONT>
<BR><FONT SIZE=3D2>>angular velocity of one object relative to =
another satisfies a </FONT>
<BR><FONT SIZE=3D2>>specified constraint.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>13)"Apparent diameter"-- determine =
time intervals during which the </FONT>
<BR><FONT SIZE=3D2>>apparent diameter of a body satisfies a =
specified constraint.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>14)"Elongation"-- determine time =
intervals during which the </FONT>
<BR><FONT SIZE=3D2>>elongation (angular separation of a body from =
the sun) of a body </FONT>
<BR><FONT SIZE=3D2>>satisfies a specified constraint.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>15)"Relative velocity"-- determine =
time intervals during which the </FONT>
<BR><FONT SIZE=3D2>>velocity of one body relative to another =
satisfies a specified </FONT>
<BR><FONT SIZE=3D2>>constraint.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>16) "User supplied"-- determine time =
intervals during which a </FONT>
<BR><FONT SIZE=3D2>>function provided by the user satisfies a =
specified constraint.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>In addition to the time oriented =
"windows/schedules" discussed </FONT>
<BR><FONT SIZE=3D2>>above, it is possible (but more work) to have =
other solutions. An </FONT>
<BR><FONT SIZE=3D2>>example might be to find a range of viewed =
latitudes and longitudes </FONT>
<BR><FONT SIZE=3D2>>for a specified time window.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>The main purpose of this note is to solicit your =
input. Are the 16 </FONT>
<BR><FONT SIZE=3D2>>constraints listed above of any use to you? Are =
there others that </FONT>
<BR><FONT SIZE=3D2>>would be more useful?</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>Regards,</FONT>
<BR><FONT SIZE=3D2>>Lee Elson</FONT>
<BR><FONT SIZE=3D2>>Lee.Elson@jpl.nasa.gov</FONT>
<BR><FONT SIZE=3D2>>818-354-4223</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT =
SIZE=3D2>>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>>Spice_announce mailing list</FONT>
<BR><FONT SIZE=3D2>>Spice_announce@naif.jpl.nasa.gov</FONT>
<BR><FONT SIZE=3D2>><A =
HREF=3D"http://naif.jpl.nasa.gov/mailman/listinfo/spice_announce" =
TARGET=3D"_blank">http://naif.jpl.nasa.gov/mailman/listinfo/spice_announ=
ce</A></FONT>
</P>
<BR>
<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>Diane Conner</FONT>
<BR><FONT SIZE=3D2>--------------------------------</FONT>
<BR><FONT SIZE=3D2>1.818.354.8586 voice =
1.818.393.4669 Fax </FONT>
<BR><FONT SIZE=3D2>SPICE: <A =
HREF=3D"https://cassini.jpl.nasa.gov/csos/io/spice/" =
TARGET=3D"_blank">https://cassini.jpl.nasa.gov/csos/io/spice/</A></FONT>=
<BR><FONT SIZE=3D2>SPICE FILES: <A =
HREF=3D"ftp://naif.jpl.nasa.gov/pub/naif/CASSINI/kernels/" =
TARGET=3D"_blank">ftp://naif.jpl.nasa.gov/pub/naif/CASSINI/kernels/</A><=
/FONT>
<BR><FONT SIZE=3D2>PDS Archive: <A =
HREF=3D"https://cassini.jpl.nasa.gov/pds_archive" =
TARGET=3D"_blank">https://cassini.jpl.nasa.gov/pds_archive</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C2DC1D.10272B80--