May throw a not implemented exception if CanAbortExpsoure is false.
- ///-
- ///
Must throw exception if camera is not idle and abort is unsuccessful (or not possible, e.g. during download).
- /// Must throw exception if hardware or communications error occurs.
- /// Must NOT throw an exception if the camera is already idle.
- ///
May throw a not implemented exception if this camera does not support PulseGuide
- ///-
- ///
guideNorth 0 North (+ declination/elevation)
- /// guideSouth 1 South (- declination/elevation)
- /// guideEast 2 East (+ right ascension/azimuth)
- /// guideWest 3 West (+ right ascension/azimuth)
- ///
Must be implemented, must not throw a NotImplementedException.
- ///May throw a not implemented exception
- ///-
- ///
0 CameraIdle At idle state, available to start exposure
- /// 1 CameraWaiting Exposure started but waiting (for shutter, trigger, filter wheel, etc.)
- /// 2 CameraExposing Exposure currently in progress
- /// 3 CameraReading CCD array is being read out (digitized)
- /// 4 CameraDownload Downloading data to PC
- /// 5 CameraError Camera error condition serious enough to prevent further operations (connection fail, etc.).
- ///
Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented by colour cameras, monochrome cameras must throw a NotImplementedException
- ///Must be implemented by colour cameras, monochrome cameras must throw a NotImplementedException
- ///Must be implemented, must not throw a NotImplementedException.
- /// It is recommended that this function be called only after aMust be implemented, must not throw a NotImplementedException.
- /// It is recommended that this function be called only after - /// aMust be implemented, must not throw a NotImplementedException.
- /// This must be a non-zero number representing the shortest possible exposure time supported by the camera model. - ///Must be implemented, must not throw a NotImplementedException.
- /// This can be used, for example, to specify the resolution of a user interface "spin control" used to dial in the exposure time. - ///Must throw a NotImplementedException if CanFastReadout is false or - /// return a boolean value if CanFastReadout is true.
- /// Must thrown an exception if noOR
- /// GAINS INDEX MODE: Index into the Gains array for the current camera gain - ///This is an optional property and can throw a NotImplementedException if Gain is not supported by the camera.
- /// The-
- ///
- GAIN VALUE MODE - The
property is a direct numeric representation of the camera's gain. - /// -
- ///
- In this mode the
and properties must return integers specifying the valid range for
- /// - The
property must return a .
- ///
- /// - In this mode the
- GAINS INDEX MODE - The
property is the selected gain's index within the array of textual gain descriptions. - /// -
- ///
- In this mode the
method returns a 0-based array of strings, which describe available gain settings e.g. "ISO 200", "ISO 1600"
- /// and must throw s.
- /// - Please note that the
array is zero based.
- ///
- /// - In this mode the
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
must return the camera's highest valid setting.
- /// must be equal to or greater than .
- /// must throw a
- ///
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
must return the camera's lowest valid setting.
- /// must be less than or equal to .
- /// must throw a
- ///
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
- The
property must return a zero-based ArrayList of available gain setting names.
- /// - The
and properties must throw s.
- ///
May throw a NotImplementedException if PercentCompleted is not supported by the camera.
- /// If valid, returns an integer between 0 and 100, where 0 indicates 0% progress (function just started) and - /// 100 indicates 100% progress (i.e. completion). - ///Must be implemented if CanFastReadout is false, must throw a NotImplementedException if - /// CanFastReadout is true.
- ///Must be implemented if CanFastReadout is false, must throw a NotImplementedException if - /// CanFastReadout is true.
- /// This property provides an array of strings, each of which describes an available readout mode of the camera. - /// At least one string must be present in the list. The user interface of a control application will typically present to the - /// user a drop-list of modes. The choice of available modes made available is entirely at the discretion of the driver author. - /// Please note that if the camera has many different modes of operation, then the most commonly adjusted settings should be in - ///May throw a NotImplementedException if the sensor's name is not known.
- ///-
- ///
- All letters shall be upper-case. - ///
- Spaces shall not be included. - ///
- Any extra suffixes that define region codes, package types, temperature range, coatings, grading, colour/monochrome, - /// etc. shall not be included. - ///
- For colour sensors, if a suffix differentiates different Bayer matrix encodings, it shall be included. - ///
- The call shall return an empty string if the sensor name is not known. - ///
-
- ///
ICX285AL-F shall be reported as ICX285
- /// KAF-8300-AXC-CD-AA shall be reported as KAF-8300
- ///
May throw a NotImplementedException if the sensor type is not known.
- ///| - /// Value | - ///- /// Enumeration | - ///- /// Meaning | - ///
| - /// 0 | - ///- /// Monochrome | - ///- /// Camera produces monochrome array with no Bayer encoding | - ///
| - /// 1 | - ///- /// Colour | - ///- /// Camera produces color image directly, requiring not Bayer decoding | - ///
| - /// 2 | - ///- /// RGGB | - ///- /// Camera produces RGGB encoded Bayer array images | - ///
| - /// 3 | - ///- /// CMYG | - ///- /// Camera produces CMYG encoded Bayer array images | - ///
| - /// 4 | - ///- /// CMYG2 | - ///- /// Camera produces CMYG2 encoded Bayer array images | - ///
| - /// 5 | - ///- /// LRGB | - ///- /// Camera produces Kodak TRUESENSE Bayer LRGB array images | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///
| - /// Y = 0 | - ///- /// R | - ///- /// G | - ///
| - /// Y = 1 | - ///- /// G | - ///- /// B | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///
| - /// Y = 0 | - ///- /// Y | - ///- /// C | - ///
| - /// Y = 1 | - ///- /// G | - ///- /// M | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///
| - /// Y = 0 | - ///- /// C | - ///- /// Y | - ///
| - /// Y = 1 | - ///- /// M | - ///- /// G | - ///
| - /// Y = 2 | - ///- /// C | - ///- /// Y | - ///
| - /// Y = 3 | - ///- /// G | - ///- /// M | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///- /// X = 2 | - ///- /// X = 3 | - ///
| - /// Y = 0 | - ///- /// L | - ///- /// R | - ///- /// L | - ///- /// G | - ///
| - /// Y = 1 | - ///- /// R | - ///- /// L | - ///- /// G | - ///- /// L | - ///
| - /// Y = 2 | - ///- /// L | - ///- /// G | - ///- /// L | - ///- /// B | - ///
| - /// Y = 3 | - ///- /// G | - ///- /// L | - ///- /// B | - ///- /// L | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///
| - /// Y = 0 | - ///- /// G | - ///- /// M | - ///
| - /// Y = 1 | - ///- /// C | - ///- /// Y | - ///
| - /// Y = 2 | - ///- /// M | - ///- /// G | - ///
| - /// Y = 3 | - ///- /// C | - ///- /// Y | - ///
OR
- /// OFFSETS INDEX MODE: Index into the Offsets array for the current camera offset - ///This is an optional property and can throw a NotImplementedException if Offset is not supported by the camera.
- /// The-
- ///
- OFFSET VALUE MODE - The
property is a direct numeric representation of the camera's offset. - /// -
- ///
- In this mode the
and properties must return integers specifying the valid range for
- /// - The
property must return a .
- ///
- /// - In this mode the
- OFFSETS INDEX MODE - The
property is the selected offset's index within the array of textual offset descriptions. - /// -
- ///
- In this mode the
method returns a 0-based array of strings, which describe available offset settings e.g. "ISO 200", "ISO 1600"
- /// and must throw s.
- /// - Please note that the
array is zero based.
- ///
- /// - In this mode the
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
must return the camera's highest valid setting.
- /// must be equal to or greater than .
- /// must throw a
- ///
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
must return the camera's lowest valid setting.
- /// must be less than or equal to .
- /// must throw a
- ///
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
- The
property must return a zero-based ArrayList of available offset setting names.
- /// - The
and properties must throw s.
- ///
This is an optional property and can throw a NotImplementedException.
- ///This is a mandatory property and must not throw a
This is a mandatory property and must not throw a
Must be implemented, must not throw a NotImplementedException.
- /// Calling this method will immediately disable hardware slewing (Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- /// See the notes for theMust be implemented, must not throw a NotImplementedException.
- ///Slaved Read must be implemented and must not throw a NotImplementedException.
- ///Slaved Write can throw a NotImplementedException.
- /// Set this property to True to enable dome-telescope hardware slaving, if supported (seeSlewing must be implemented and must not throw a NotImplementedException.
- /// Raises an error ifMust be implemented, must not throw a NotImplementedException.
- /// For each valid slot number (from 0 to N-1), reports the focus offset for the given filter position. These values are focuser and filter dependent, and would usually be set up by the user via - /// the SetupDialog. The number of slots N can be determined from the length of the array. If focuser offsets are not available, then it should report back 0 for all array values. - ///Must be implemented, must not throw a NotImplementedException.
- /// For each valid slot number (from 0 to N-1), reports the name given to the filter position. These names would usually be set up by the user via the - /// SetupDialog. The number of slots N can be determined from the length of the array. If filter names are not available, then it should report back "Filter 1", "Filter 2", etc. - ///Must be implemented, must not throw a PropertyNotImplementedException.
- ///Must be implemented
Must be implemented
Must be implemented
- /// For most focusers this is the same as theMust be implemented
- /// The focuser can step between 0 andCan throw a not implemented exception
Valid only for absolute positioning focusers (see theCan throw a not implemented exception
Must throw an exception if the focuser does not intrinsically know what the step size is.TempComp Read must be implemented and must not throw a NotImplementedException.
- ///TempComp Write can throw a NotImplementedException.
- /// If theMust be implemented
- /// Will be True only if the focuser's temperature compensation can be turned on and off via theCan throw a not implemented exception
- /// Raises an exception if ambient temperature is not available. Commonly available on focusers with a built-in temperature compensation mode. - ///Can throw a not implemented exception
Some focusers may not support this function, in which case an exception will be raised. - ///Must be implemented
- ///Must Not throw a NotImplementedException when the specified sensor Is implemented but must throw a NotImplementedException when the specified sensor Is Not implemented.
- ///Must Not throw a NotImplementedException when the specified sensor Is implemented - /// but must throw a NotImplementedException when the specified sensor Is Not implemented.
- ///Optional method, can throw a MethodNotImplementedException
- ///Mandatory property, must be implemented, can NOT throw a NotImplementedException
- ///Optional property, can throw a NotImplementedException
- /// This property should return a value between 0.0 and 100.0 where 0.0 = clear sky and 100.0 = 100% cloud coverage - ///Optional property, can throw a NotImplementedException when the
Mandatory property, must NOT throw a NotImplementedException when the
Optional property, can throw a NotImplementedException when the
Mandatory property, must NOT throw a NotImplementedException when the
Optional property, can throw a NotImplementedException
- ///Optional property, can throw a NotImplementedException
- ///-
- ///
Light rain — when the precipitation rate is less than 2.5 mm (0.098 in) per hour
- /// Moderate rain — when the precipitation rate is between 2.5 mm (0.098 in) and 10 mm (0.39 in) per hour
- /// Heavy rain — when the precipitation rate is between 10 mm (0.39 in) and 50 mm (2.0 in) per hour
- /// Violent rain — when the precipitation rate is > 50 mm (2.0 in) per hour
- ///
Optional property, can throw a NotImplementedException
- /// This property returns the sky brightness measured in Lux. - ///-
- ///
0.0001 lux Moonless, overcast night sky (starlight)
- /// 0.002 lux Moonless clear night sky with airglow
- /// 0.27–1.0 lux Full moon on a clear night
- /// 3.4 lux Dark limit of civil twilight under a clear sky
- /// 50 lux Family living room lights (Australia, 1998)
- /// 80 lux Office building hallway/toilet lighting
- /// 100 lux Very dark overcast day
- /// 320–500 lux Office lighting
- /// 400 lux Sunrise or sunset on a clear day.
- /// 1000 lux Overcast day; typical TV studio lighting
- /// 10000–25000 lux Full daylight (not direct sun)
- /// 32000–100000 lux Direct sunlight
- ///
Optional property, can throw a NotImplementedException
- ///| - /// Sky Quality (mag/arcsec2) | - ///- /// Description | - ///
| - /// 22.0 | - ///- /// By convention, this is often assumed to be the average brightness of a moonless night sky that's completely free of artificial light pollution. | - ///
| - /// 21.0 | - ///- /// This is typical for a rural area with a medium-sized city not far away. It's comparable to the glow of the brightest section of the northern Milky Way, from Cygnus through Perseus. | - ///
| - /// 20.0 | - ///- /// This is typical for the outer suburbs of a major metropolis. The summer Milky Way is readily visible but severely washed out. | - ///
| - /// 19.0 | - ///- /// Typical for a suburb with widely spaced single-family homes. It's a little brighter than a remote rural site at the end of nautical twilight, when the Sun is 12° below the horizon. | - ///
| - /// 18.0 | - ///- /// Bright suburb or dark urban neighborhood. It's also a typical zenith skyglow at a rural site when the Moon is full. The Milky Way is invisible, or nearly so. | - ///
| - /// 17.0 | - ///- /// Typical near the center of a major city. | - ///
| - /// 13.0 | - ///- /// The zenith skyglow at the end of civil twilight, roughly a half hour after sunset, when the Sun is 6° below the horizon. Venus and Jupiter are easy to see, but bright stars are just beginning to appear. | - ///
| - /// 7.0 | - ///- /// The zenith skyglow at sunrise or sunset | - ///
Optional property, can throw a NotImplementedException
- ///Optional property, can throw a NotImplementedException
- ///Optional property, can throw a NotImplementedException
- ///Optional property, can throw a NotImplementedException
- /// The returned value must be between 0.0 and 360.0, interpreted according to the meteorological standard, where a special value of 0.0 is returned when the wind speed is 0.0. - /// Wind direction is measured clockwise from north, through east, where East=90.0, South=180.0, West=270.0 and North=360.0. - ///Optional property, can throw a NotImplementedException
- /// The units of this property are metres per second. Driver and application authors can use the ASCOM.Tools.Utilities.ConvertUnits method - /// to convert these units to and from miles per hour or knots. - ///Optional property, can throw a NotImplementedException
- /// The units of this property are metres per second. Driver and application authors can use the ASCOM.Tools.Utilities.ConvertUnits method - /// to convert these units to and from miles per hour or knots. - ///Must be implemented and must always return True for the IRotatorV3 interface or later.
- ///Must be implemented.
- ///Must be implemented.
- ///SPECIFICATION REVISION - IRotatorV3 - Platform 6.5
- ///Must be implemented.
- ///Optional - can throw a not implemented exception
- ///Must be implemented.
- ///Optional - can throw a not implemented exception
Must be implemented.
- ///Must be implemented.
- ///Must be implemented.
- ///Introduced in IRotatorV3.
- /// Returns the mechanical position of the rotator, which is equivalent to the IRotatorV2Must be implemented.
- ///Introduced in IRotatorV3.
- /// Once this method has been called and the sync offset determined, both theMust be implemented.
- ///Must be implemented and must not throw a NotImplementedException.
- ///Must be implemented, must not throw an ASCOM.NotImplementedException
- ///Must be implemented, must not throw a
-
- ///
Sets the device to a known state on connection
- /// Throws an until the client software has set the device state for the first time
- ///
Must be implemented, must not throw an ASCOM.NotImplementedException
- ///Must be implemented, must not throw an ASCOM.NotImplementedException
- ///Must be implemented, must not throw a
-
- ///
Sets the device to a known state on connection
- /// Throws an until the client software has set the device state for the first time
- ///
Must be implemented, must not throw a
Devices are numbered from 0 to
Must be implemented, must not throw a
Must be implemented, must not throw a
Must be implemented, must not throw
Can throw a
Can throw a
Can throw a
Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- /// See the description ofMust be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// This is only available for telescope Interface Versions 2 and later. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// This will always return False for mounts that do not have to be flipped. - /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// If this is true, theMust be implemented, must not throw a NotImplementedException.
- /// If this is true, theMust be implemented, must not throw a NotImplementedException.
- /// If this is true, theMust be implemented, must not throw a NotImplementedException.
- /// If this is true, theMust be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// If this is true, thenMust be implemented, must not throw a NotImplementedException.
- ///DeclinationRate Read must be implemented and must not throw a NotImplementedException.
- ///DeclinationRate Write can throw a NotImplementedException.
- /// This property, together with-
- ///
The property value represents an offset from zero motion.
- /// If is False, this property will always return 0.
- /// To discover whether this feature is supported, test the property.
- /// The supported range of this property is telescope specific, however, if this feature is supported, - /// it can be expected that the range is sufficient to allow correction of guiding errors caused by moderate misalignment - /// and periodic error.
- /// If this property is non-zero when an equatorial slew is initiated, the telescope should continue to update the slew - /// destination coordinates at the given offset rate.
- /// This will allow precise slews to a fast-moving target with a slow-slewing telescope.
- /// When the slew completes, the and properties should reflect the final (adjusted) destination.
- /// The units of this property are arcseconds per SI (atomic) second. Please note that for historic reasons the units of the property are seconds of RA per sidereal second.
- ///
-
- ///
If the driver does not know whether the attached telescope does its own refraction, and if the driver does not itself calculate - /// refraction, this property (if implemented) must raise an error when read.
- /// Writing to this property is optional. Often, a telescope (or its driver) calculates refraction using standard atmospheric parameters.
- /// If the client wishes to calculate a more accurate refraction, then this property could be set to False and these - /// client-refracted coordinates used.
- /// If disabling the telescope or driver's refraction is not supported, the driver must raise an error when an attempt to set - /// this property to False is made.
- /// Setting this property to True for a telescope or driver that does refraction, or to False for a telescope or driver that - /// does not do refraction, shall not raise an error. It shall have no effect.
- ///
Must be implemented, must not throw a NotImplementedException.
- /// Most amateur telescopes use topocentric coordinates. This coordinate system is simply the apparent position in the sky - /// (possibly uncorrected for atmospheric refraction) for "here and now", thus these are the coordinates that one would use with digital setting - /// circles and most amateur scopes. More sophisticated telescopes use one of the standard reference systems established by professional astronomers. - /// The most common is the Julian Epoch 2000 (J2000). These instruments apply corrections for precession,nutation, aberration, etc. to adjust the coordinates - /// from the standard system to the pointing direction for the time and location of "here and now". - ///-
- ///
To discover whether this feature is supported, test the property.
- /// The supported range of this property is telescope specific, however, if this feature is supported, it can be expected that the range is sufficient to - /// allow correction of guiding errors caused by moderate misalignment and periodic error.
- /// If a telescope does not support separate guiding rates in Right Ascension and Declination, then it is permissible for and GuideRateDeclination to be tied together. - /// In this case, changing one of the two properties will cause a change in the other.
- /// Mounts must start up with a known or default declination guide rate, and this property must return that known/default guide rate until changed.
- ///
-
- ///
To discover whether this feature is supported, test the property.
- /// The supported range of this property is telescope specific, however, if this feature is supported, it can be expected that the range is sufficient to allow correction of guiding errors caused by moderate - /// misalignment and periodic error.
- /// If a telescope does not support separate guiding rates in Right Ascension and Declination, then it is permissible for GuideRateRightAscension and to be tied together. - /// In this case, changing one of the two properties will cause a change in the other.
- /// Mounts must start up with a known or default right ascension guide rate, and this property must return that known/default guide rate until changed.
- ///
-
- ///
The movement rate must be within the value(s) obtained from a object in the - /// the collection. This is a signed value with negative rates moving in the opposite direction to positive rates.
- /// The values specified in are absolute, unsigned values and apply to both directions, determined by the sign used in this command.
- /// The value of must be True if the telescope is moving about any of its axes as a result of this method being called. - /// This can be used to simulate a handbox by initiating motion with the MouseDown event and stopping the motion with the MouseUp event.
- /// When the motion is stopped by setting the rate to zero the scope will be set to the previous or to no movement, depending on the state of the property.
- /// It may be possible to implement satellite tracking by using the method to move the scope in the required manner to track a satellite.
- ///
-
- ///
Raises an error if is true.
- /// The property must be True during pulse-guiding.
- /// The rate of motion for movements about the right ascension axis is - /// specified by the property. The rate of motion - /// for movements about the declination axis is specified by the - /// property. These two rates may be tied together - /// into a single rate, depending on the driver's implementation - /// and the capabilities of the telescope.
- ///
Must be implemented, must not throw a NotImplementedException.
- /// Reading the property will raise an error if the value is unavailable. - ///RightAscensionRate Read must be implemented and must not throw a NotImplementedException.
- ///RightAscensionRate Write can throw a NotImplementedException.
- /// This property, together with-
- ///
If this property is zero, tracking will be at the selected .
- /// If is False, this property must always return 0.
- /// To discover whether this feature is supported, test the The units of this property are seconds of right ascension per sidereal second. Please note that for historic reasons the units of the property are arcseconds per SI second.
- /// To convert a given rate in (the more common) units of sidereal seconds per UTC (clock) second, multiply the value by 0.9972695677 - /// (the number of UTC seconds in a sidereal second) then set the property. Please note that these units were chosen for the Telescope V1 standard, - /// and in retrospect, this was an unfortunate choice. However, to maintain backwards compatibility, the units cannot be changed. - /// A simple multiplication is all that's needed, as noted. The supported range of this property is telescope specific, however, - /// if this feature is supported, it can be expected that the range is sufficient to allow correction of guiding errors - /// caused by moderate misalignment and periodic error.
- /// If this property is non-zero when an equatorial slew is initiated, the telescope should continue to update the slew destination coordinates - /// at the given offset rate. This will allow precise slews to a fast-moving target with a slow-slewing telescope. When the slew completes, - /// the and properties should reflect the final (adjusted) destination. This is not a required - /// feature of this specification, however it is desirable.
- /// Use the property to enable and disable sidereal tracking (if supported).
- ///
-
- ///
Normal ( ) Where the mechanical Dec is in the range -90 deg to +90 deg
- /// Beyond the pole ( ) Where the mechanical Dec is in the range -180 deg to -90 deg or +90 deg to +180 deg.
- ///
-
- ///
HA_sky = HA_mech
- /// Dec_sky = Dec_mech
- ///
-
- ///
HA_sky = HA_mech + 12h, expressed in range ± 12h
- /// Dec_sky = 180d - Dec_mech, expressed in range ± 90d
- ///
-
- ///
pierEast Normal pointing state
- /// pierWest Beyond the pole pointing state
- ///
-
- ///
pierEast = abs(mechanical dec) <= 90 deg
- /// pierWest = abs(mechanical Dec) > 90 deg
- ///
Must be implemented, must not throw a NotImplementedException.
- /// It is required for a driver to calculate this from the system clock if the telescope - /// has no accessible source of sidereal time. Local Apparent Sidereal Time is the sidereal - /// time used for pointing telescopes, and thus must be calculated from the Greenwich Mean - /// Sidereal time, longitude, nutation in longitude and true ecliptic obliquity. - ///Deprecated for client applications.
- ///Deprecated for client applications.
- ///Deprecated for client applications.
- ///Tracking Read must be implemented and must not throw a NotImplementedException.
- ///Tracking Write can throw a NotImplementedException.
- /// Changing the value of this property will turn the sidereal drive on and off. - /// However, some telescopes may not support changing the value of this property - /// and thus may not support turning tracking on and off. - /// See theTrackingRate Read must be implemented and must not throw a NotImplementedException.
- ///TrackingRate Write can throw a NotImplementedException.
- /// Supported rates (one of theMust be implemented and must not throw a NotImplementedException.
- /// At a minimum, this must contain an item forUTCDate Read must be implemented and must not throw a NotImplementedException.
- ///UTCDate Write can throw a NotImplementedException.
- /// The driver must calculate this from the system clock if the telescope has no accessible source of UTC time. In this case, the property must not be writeable (this would change the system clock!) and will instead raise an error. - /// However, it is permitted to change the telescope's internal UTC clock if it is being used for this property. This allows clients to adjust the telescope's UTC clock as needed for accuracy. Reading the property - /// will raise an error if the value has never been set or is otherwise unavailable. - ///Can throw a not implemented exception
- /// This method is intended for use in all current and future device types and to avoid name clashes, management of action names - /// is important from day 1. A two-part naming convention will be adopted - DeviceType:UniqueActionName where: - ///-
- ///
DeviceType is the string name of the device type e.g. Telescope, Camera, Switch etc.
- /// UniqueActionName is a single word, or multiple words joined by underscore characters, that sensibly describes the action to be performed.
- ///
May throw a NotImplementedException.
- ///May throw a NotImplementedException.
- ///May throw a NotImplementedException.
- ///Must be implemented
This method must return an empty
+ /// <PropertyGroup Condition = "$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'android'">
+ /// <UseNativeHttpHandler>false</UseNativeHttpHandler>
+ /// </PropertyGroup>
+ ///
+ ///
- /// 0 ... everything is ok
+ /// 0 ... everything is OK
/// 1 ... invalid value of 'Accuracy'
/// 2 ... invalid value of 'Method'
/// > 10 ... 10 + error from function 'CioLocation'
@@ -690,8 +767,8 @@ public static short Cel2Ter(double JdHigh, double JdLow, double DeltaT, Method M
///
/// 0 ... Everything OK
/// 1 ... Invalid value of 'Type'.
@@ -706,7 +783,7 @@ public static short CelPole(double Tjd, PoleOffsetCorrection Type, double Dpole1
}
///
- /// Calaculate an array of CIO RA values around a given date
+ /// Calculate an array of CIO RA values around a given date
///
/// TDB Julian date.
/// Number of Julian dates and right ascension values requested (not less than 2 or more than 20).
@@ -718,7 +795,7 @@ public static short CelPole(double Tjd, PoleOffsetCorrection Type, double Dpole1
/// 2 ... 'JdTdb' not in the range of the CIO file;
/// 3 ... 'NPts' out of range
/// 4 ... unable to allocate memory for the internal 't' array;
- /// 5 ... unable to allocate memory for the internal 'ra' array;
+ /// 5 ... unable to allocate memory for the internal 'RA' array;
/// 6 ... 'JdTdb' is too close to either end of the CIO file; unable to put 'NPts' data points into the output object.
///
/// 0 ... Everything OK
/// 1 ... Invalid value of 'Origin'
@@ -1027,13 +1104,13 @@ public static void Equ2Gal(double RaI, double DecI, ref double GLon, ref double
/// UT1 Julian date.
/// Difference TT-UT1 at 'jd_ut1', in seconds.
/// Selection for accuracy
- /// onventionally-defined x coordinate of celestial intermediate pole with respect to ITRS reference pole, in arcseconds.
+ /// Conventionally-defined x coordinate of celestial intermediate pole with respect to ITRS reference pole, in arcseconds.
/// Conventionally-defined y coordinate of celestial intermediate pole with respect to ITRS reference pole, in arcseconds.
/// Structure containing observer's location
/// Topocentric right ascension of object of interest, in hours, referred to true equator and equinox of date.
/// Topocentric declination of object of interest, in degrees, referred to true equator and equinox of date.
/// Refraction option. 0 ... no refraction; 1 ... include refraction, using 'standard' atmospheric conditions;
- /// 2 ... include refraction, using atmospheric parametersinput in the 'Location' structure.
+ /// 2 ... include refraction, using atmospheric parameters input in the 'Location' structure.
/// Topocentric zenith distance in degrees, affected by refraction if 'ref_option' is non-zero.
/// Topocentric azimuth (measured east from north) in degrees.
/// Topocentric right ascension of object of interest, in hours, referred to true equator and
@@ -1082,7 +1159,7 @@ public static void Equ2Hor(double Jd_Ut1, double DeltT, Accuracy Accuracy, doubl
/// The expression used is taken from the note to IAU Resolution B1.8 of 2000. 1. The algorithm used
/// here is equivalent to the canonical theta = 0.7790572732640 + 1.00273781191135448 * t, where t is the time
/// in days from J2000 (t = JdHigh + JdLow - T0), but it avoids many two-PI 'wraps' that
- /// decrease precision (adopted from SOFA Fortran routine iau_era00; see also expression at top
+ /// decrease precision (adopted from SOFA FORTRAN routine iau_era00; see also expression at top
/// of page 35 of IERS Conventions (1996)).
public static double Era(double JdHigh, double JdLow)
{
@@ -1343,7 +1420,7 @@ public static double JulianDate(short Year, short Month, short Day, double Hour)
/// Computes the geocentric position of a solar system body, as antedated for light-time.
///
- /// 0 ... everything is ok
+ /// 0 ... everything is OK
/// 1 ... invalid value of 'Accuracy'
/// 2 ... invalid value of 'Method'
/// > 10 ... 10 + error from function 'CioLocation'
@@ -2067,7 +2148,9 @@ public static void Terra(OnSurface Location, double St, ref double[] Pos, ref do
/// = 1 ... Invalid value of 'Where' in structure 'Location'.
/// > 10 ... Error code from function 'Place'.
/// -
+ ///
utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day. + /// However, JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the length is 86399, 86400 or 86401 SI seconds. + ///Applications should use the function iauDtf2d to convert from calendar date and time of day into 2-part quasi Julian Date, as it implements the leap-second-ambiguity convention just described.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// UT1-UTC is tabulated in IERS bulletins. It increases by exactly one second at the end of each positive UTC leap second, introduced in order to keep UT1-UTC within +/- 0.9s. n.b. This practice is under review, and in the future UT1-UTC may grow essentially without limit.
+ /// The geographical coordinates are with respect to the WGS84 reference ellipsoid. TAKE CARE WITH THE LONGITUDE SIGN: the longitude required by the present function is east-positive (i.e. right-handed), in accordance with geographical convention.
+ /// The polar motion xp,yp can be obtained from IERS bulletins. The values are the coordinates (in radians) of the Celestial Intermediate Pole with respect to the International Terrestrial + /// Reference System (see IERS Conventions 2003), measured along the meridians 0 and 90 deg west respectively. For many applications, xp and yp can be set to zero.
+ /// If hm, the height above the ellipsoid of the observing station in meters, is not known but phpa, the pressure in hPa (=mB), is available, an adequate estimate of hm can be obtained from the expression: + /// hm = -29.3 * tsl * log ( phpa / 1013.25 );
+ ///where tsl is the approximate sea-level air temperature in K (See Astrophysical Quantities, C.W.Allen, 3rd edition, section 52). Similarly, if the pressure phpa is not known, it can be estimated from the height of the observing station, hm, as follows: + ///phpa = 1013.25 * exp ( -hm / ( 29.3 * tsl ) );
+ ///Note, however, that the refraction is nearly proportional to the pressure and that an accurate phpa value is important for precise work.
+ /// The argument wl specifies the observing wavelength in micrometers. The transition from optical to radio is assumed to occur at 100 micrometers (about 3000 GHz).
+ /// "Observed" Az,ZD means the position that would be seen by a perfect geodetically aligned theodolite. (Zenith distance is used rather than altitude in order to reflect the fact that no + /// allowance is made for depression of the horizon.) This is related to the observed HA,Dec via the standard rotation, using the geodetic latitude (corrected for polar motion), while the observed HA and RA are related simply through the Earth rotation + /// angle and the site longitude. "Observed" RA,Dec or HA,Dec thus means the position that would be seen by a perfect equatorial with its polar axis aligned to the Earth's axis of rotation.
+ /// The accuracy of the result is limited by the corrections for refraction, which use a simple A*tan(z) + B*tan^3(z) model. Providing the meteorological parameters are known accurately and there are no gross local effects, the predicted astrometric + /// coordinates should be within 0.05 arcsec (optical) or 1 arcsec (radio) for a zenith distance of less than 70 degrees, better than 30 arcsec (optical or radio) at 85 degrees and better than 20 arcmin (optical) or 30 arcmin (radio) at the horizon.
+ /// The complementary functions iauAtio13 and iauAtoi13 are self-consistent to better than 1 microarcsecond all over the celestial sphere.
+ /// It is advisable to take great care with units, as even unlikely values of the input parameters are accepted and processed in accordance with the models used.
+ ///
-
- ///
utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day. - /// However, JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the length is 86399, 86400 or 86401 SI seconds. - ///Applications should use the function iauDtf2d to convert from calendar date and time of day into 2-part quasi Julian Date, as it implements the leap-second-ambiguity convention just described.
- /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
- /// UT1-UTC is tabulated in IERS bulletins. It increases by exactly one second at the end of each positive UTC leap second, introduced in order to keep UT1-UTC within +/- 0.9s. n.b. This practice is under review, and in the future UT1-UTC may grow essentially without limit.
- /// The geographical coordinates are with respect to the WGS84 reference ellipsoid. TAKE CARE WITH THE LONGITUDE SIGN: the longitude required by the present function is east-positive (i.e. right-handed), in accordance with geographical convention.
- /// The polar motion xp,yp can be obtained from IERS bulletins. The values are the coordinates (in radians) of the Celestial Intermediate Pole with respect to the International Terrestrial - /// Reference System (see IERS Conventions 2003), measured along the meridians 0 and 90 deg west respectively. For many applications, xp and yp can be set to zero.
- /// If hm, the height above the ellipsoid of the observing station in meters, is not known but phpa, the pressure in hPa (=mB), is available, an adequate estimate of hm can be obtained from the expression: - /// hm = -29.3 * tsl * log ( phpa / 1013.25 );
- ///where tsl is the approximate sea-level air temperature in K (See Astrophysical Quantities, C.W.Allen, 3rd edition, section 52). Similarly, if the pressure phpa is not known, it can be estimated from the height of the observing station, hm, as follows: - ///phpa = 1013.25 * exp ( -hm / ( 29.3 * tsl ) );
- ///Note, however, that the refraction is nearly proportional to the pressure and that an accurate phpa value is important for precise work.
- /// The argument wl specifies the observing wavelength in micrometers. The transition from optical to radio is assumed to occur at 100 micrometers (about 3000 GHz).
- /// "Observed" Az,ZD means the position that would be seen by a perfect geodetically aligned theodolite. (Zenith distance is used rather than altitude in order to reflect the fact that no - /// allowance is made for depression of the horizon.) This is related to the observed HA,Dec via the standard rotation, using the geodetic latitude (corrected for polar motion), while the observed HA and RA are related simply through the Earth rotation - /// angle and the site longitude. "Observed" RA,Dec or HA,Dec thus means the position that would be seen by a perfect equatorial with its polar axis aligned to the Earth's axis of rotation.
- /// The accuracy of the result is limited by the corrections for refraction, which use a simple A*tan(z) + B*tan^3(z) model. Providing the meteorological parameters are known accurately and there are no gross local effects, the predicted astrometric - /// coordinates should be within 0.05 arcsec (optical) or 1 arcsec (radio) for a zenith distance of less than 70 degrees, better than 30 arcsec (optical or radio) at 85 degrees and better than 20 arcmin (optical) or 30 arcmin (radio) at the horizon.
- /// The complementary functions iauAtio13 and iauAtoi13 are self-consistent to better than 1 microarcsecond all over the celestial sphere.
- /// It is advisable to take great care with units, as even unlikely values of the input parameters are accepted and processed in accordance with the models used.
- ///
-
- ///
Scale identifies the time scale. Only the value "UTC" (in upper case) is significant, and enables handling of leap seconds (see Note 4).
- /// For calendar conventions and limitations, see iauCal2jd.
- /// The sum of the results, d1+d2, is Julian Date, where normally d1 is the Julian Day Number and d2 is the fraction of a day. In the case of UTC, where the use of JD is problematical, special conventions apply: see the next note.
- /// JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The SOFA internal convention is that the quasi-JD day represents UTC days whether the length is 86399, - /// 86400 or 86401 SI seconds. In the 1960-1972 era there were smaller jumps (in either direction) each time the linear UTC(TAI) expression was changed, and these "mini-leaps" are also included in the SOFA convention.
- /// The warning status "time is after end of day" usually means that the sec argument is greater than 60.0. However, in a day ending in a leap second the limit changes to 61.0 (or 59.0 in the case of a negative leap second).
- /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
- /// Only in the case of continuous and regular time scales (TAI, TT, TCG, TCB and TDB) is the result d1+d2 a Julian Date, strictly speaking. In the other cases (UT1 and UTC) the result must be - /// used with circumspection; in particular the difference between two such results cannot be interpreted as a precise time interval.
- ///
-
- ///
The TT date date1+date2 is a Julian Date, apportioned in any convenient way between the two arguments. For example, JD(TT)=2450123.7 could be expressed in any of these ways, among others: - /// - ///
- ///- /// - /// - /// - /// - ///- /// Date 1 - ///- /// Date 2 - ///- /// Method - ///- /// - ///- /// 2450123.7 - ///- /// 0.0 - ///- /// JD method - ///- /// - ///- /// 2451545.0 - ///- /// -1421.3 - ///- /// J2000 method - ///- /// - ///- /// 2400000.5 - ///- /// 50123.2 - ///- /// MJD method - ///- /// - ///- /// 2450123.5 - ///- /// 0.2 - ///- /// Date and time method - ///The JD method is the most natural and convenient to use in cases where the loss of several decimal digits of resolution is acceptable. The J2000 method is best matched to the way the argument is handled internally - /// and will deliver the optimum resolution. The MJD method and the date and time methods are both good compromises between resolution and convenience. For most applications of this function the choice will not be at all critical. - ///
- /// The equation of the origins is the distance between the true equinox and the celestial intermediate origin and, equivalently, the difference between Earth rotation angle and Greenwich - /// apparent sidereal time (ERA-GST). It comprises the precession (since J2000.0) in right ascension plus the equation of the equinoxes (including the small correction terms).
- ///
-
+ ///
Scale identifies the time scale. Only the value "UTC" (in upper case) is significant, and enables handling of leap seconds (see Note 4).
+ /// For calendar conventions and limitations, see iauCal2jd.
+ /// The sum of the results, d1+d2, is Julian Date, where normally d1 is the Julian Day Number and d2 is the fraction of a day. In the case of UTC, where the use of JD is problematical, special conventions apply: see the next note.
+ /// JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The SOFA internal convention is that the quasi-JD day represents UTC days whether the length is 86399, + /// 86400 or 86401 SI seconds. In the 1960-1972 era there were smaller jumps (in either direction) each time the linear UTC(TAI) expression was changed, and these "mini-leaps" are also included in the SOFA convention.
+ /// The warning status "time is after end of day" usually means that the sec argument is greater than 60.0. However, in a day ending in a leap second the limit changes to 61.0 (or 59.0 in the case of a negative leap second).
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// Only in the case of continuous and regular time scales (TAI, TT, TCG, TCB and TDB) is the result d1+d2 a Julian Date, strictly speaking. In the other cases (UT1 and UTC) the result must be + /// used with circumspection; in particular the difference between two such results cannot be interpreted as a precise time interval.
+ ///
-
+ ///
The TT date date1+date2 is a Julian Date, apportioned in any convenient way between the two arguments. For example, JD(TT)=2450123.7 could be expressed in any of these ways, among others: + /// + ///
+ ///+ /// + /// + /// + /// + ///+ /// Date 1 + ///+ /// Date 2 + ///+ /// Method + ///+ /// + ///+ /// 2450123.7 + ///+ /// 0.0 + ///+ /// JD method + ///+ /// + ///+ /// 2451545.0 + ///+ /// -1421.3 + ///+ /// J2000 method + ///+ /// + ///+ /// 2400000.5 + ///+ /// 50123.2 + ///+ /// MJD method + ///+ /// + ///+ /// 2450123.5 + ///+ /// 0.2 + ///+ /// Date and time method + ///The JD method is the most natural and convenient to use in cases where the loss of several decimal digits of resolution is acceptable. The J2000 method is best matched to the way the argument is handled internally + /// and will deliver the optimum resolution. The MJD method and the date and time methods are both good compromises between resolution and convenience. For most applications of this function the choice will not be at all critical. + ///
+ /// The equation of the origins is the distance between the true equinox and the celestial intermediate origin and, equivalently, the difference between Earth rotation angle and Greenwich + /// apparent sidereal time (ERA-GST). It comprises the precession (since J2000.0) in right ascension plus the equation of the equinoxes (including the small correction terms).
+ ///
-
- ///
tai1+tai2 is Julian Date, apportioned in any convenient way between the two arguments, for example where tai1 is the Julian Day Number and tai2 is the fraction of a day. The returned - /// tt1,tt2 follow suit.
+ /// tai1+tai2 is Julian Date, apportioned in any convenient way between the two arguments, for example where tai1 is the Julian Day Number and tai2 is the fraction of a day. The returned + /// tt1,tt2 follow suit.
+ ///
-
+ ///
tai1+tai2 is Julian Date, apportioned in any convenient way between the two arguments, for example where tai1 is the Julian Day Number and tai2 is the fraction of a day. The returned utc1 + /// and utc2 form an analogous pair, except that a special convention is used, to deal with the problem of leap seconds - see the next note.
+ /// JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the + /// length is 86399, 86400 or 86401 SI seconds. In the 1960-1972 era there were smaller jumps (in either direction) each time the linear UTC(TAI) expression was changed, and these "mini-leaps are also included in the SOFA convention.
+ /// The function iauD2dtf can be used to transform the UTC quasi-JD into calendar date and clock time, including UTC leap second handling.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ ///
-
+ ///
The result is computed even if any of the range checks fail.
+ /// Negative ihour, imin and/or sec produce a warning status, but the absolute value is used in the conversion.
+ /// If there are multiple errors, the status value reflects only the first, the smallest taking precedence.
///
-
- ///
The result is computed even if any of the range checks fail.
- /// Negative ihour, imin and/or sec produce a warning status, but the absolute value is used in the conversion.
- /// If there are multiple errors, the status value reflects only the first, the smallest taking precedence.
- ///
-
- ///
tai1+tai2 is Julian Date, apportioned in any convenient way between the two arguments, for example where tai1 is the Julian Day Number and tai2 is the fraction of a day. The returned utc1 - /// and utc2 form an analogous pair, except that a special convention is used, to deal with the problem of leap seconds - see the next note.
- /// JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the - /// length is 86399, 86400 or 86401 SI seconds. In the 1960-1972 era there were smaller jumps (in either direction) each time the linear UTC(TAI) expression was changed, and these "mini-leaps are also included in the SOFA convention.
- /// The function iauD2dtf can be used to transform the UTC quasi-JD into calendar date and clock time, including UTC leap second handling.
- /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
- ///
Must be implemented
This method must return an emptyCan throw a not implemented exception
- /// This method is intended for use in all current and future device types and to avoid name clashes, management of action names - /// is important from day 1. A two-part naming convention will be adopted - DeviceType:UniqueActionName where: - ///-
- ///
DeviceType is the string name of the device type e.g. Telescope, Camera, Switch etc.
- /// UniqueActionName is a single word, or multiple words joined by underscore characters, that sensibly describes the action to be performed.
- ///
May throw a NotImplementedException.
- ///May throw a NotImplementedException.
- ///May throw a NotImplementedException.
- ///-
- ///
0 CameraIdle At idle state, available to start exposure
- /// 1 CameraWaiting Exposure started but waiting (for shutter, trigger, filter wheel, etc.)
- /// 2 CameraExposing Exposure currently in progress
- /// 3 CameraReading CCD array is being read out (digitized)
- /// 4 CameraDownload Downloading data to PC
- /// 5 CameraError Camera error condition serious enough to prevent further operations (connection fail, etc.).
- ///
Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented by colour cameras, monochrome cameras must throw a NotImplementedException
- ///Must be implemented by colour cameras, monochrome cameras must throw a NotImplementedException
- ///Must be implemented, must not throw a NotImplementedException.
- /// It is recommended that this function be called only after aMust be implemented, must not throw a NotImplementedException.
- /// It is recommended that this function be called only after - /// aMust be implemented, must not throw a NotImplementedException.
- /// This must be a non-zero number representing the shortest possible exposure time supported by the camera model. - ///Must be implemented, must not throw a NotImplementedException.
- /// This can be used, for example, to specify the resolution of a user interface "spin control" used to dial in the exposure time. - ///Must throw a NotImplementedException if CanFastReadout is false or - /// return a boolean value if CanFastReadout is true.
- /// Must thrown an exception if noOR
- /// GAINS INDEX MODE: Index into the Gains array for the current camera gain - ///This is an optional property and can throw a NotImplementedException if Gain is not supported by the camera.
- /// The-
- ///
- GAIN VALUE MODE - The
property is a direct numeric representation of the camera's gain. - /// -
- ///
- In this mode the
and properties must return integers specifying the valid range for
- /// - The
property must return a .
- ///
- /// - In this mode the
- GAINS INDEX MODE - The
property is the selected gain's index within the array of textual gain descriptions. - /// -
- ///
- In this mode the
method returns a 0-based array of strings, which describe available gain settings e.g. "ISO 200", "ISO 1600"
- /// and must throw s.
- /// - Please note that the
array is zero based.
- ///
- /// - In this mode the
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
must return the camera's highest valid setting.
- /// must be equal to or greater than .
- /// must throw a
- ///
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
must return the camera's lowest valid setting.
- /// must be less than or equal to .
- /// must throw a
- ///
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
- The
property must return a zero-based ArrayList of available gain setting names.
- /// - The
and properties must throw s.
- ///
May throw a NotImplementedException if PercentCompleted is not supported by the camera.
- /// If valid, returns an integer between 0 and 100, where 0 indicates 0% progress (function just started) and - /// 100 indicates 100% progress (i.e. completion). - ///Must be implemented if CanFastReadout is false, must throw a NotImplementedException if - /// CanFastReadout is true.
- ///Must be implemented if CanFastReadout is false, must throw a NotImplementedException if - /// CanFastReadout is true.
- /// This property provides an array of strings, each of which describes an available readout mode of the camera. - /// At least one string must be present in the list. The user interface of a control application will typically present to the - /// user a drop-list of modes. The choice of available modes made available is entirely at the discretion of the driver author. - /// Please note that if the camera has many different modes of operation, then the most commonly adjusted settings should be in - ///May throw a NotImplementedException if the sensor's name is not known.
- ///-
- ///
- All letters shall be upper-case. - ///
- Spaces shall not be included. - ///
- Any extra suffixes that define region codes, package types, temperature range, coatings, grading, colour/monochrome, - /// etc. shall not be included. - ///
- For colour sensors, if a suffix differentiates different Bayer matrix encodings, it shall be included. - ///
- The call shall return an empty string if the sensor name is not known. - ///
-
- ///
ICX285AL-F shall be reported as ICX285
- /// KAF-8300-AXC-CD-AA shall be reported as KAF-8300
- ///
May throw a NotImplementedException if the sensor type is not known.
- ///| - /// Value | - ///- /// Enumeration | - ///- /// Meaning | - ///
| - /// 0 | - ///- /// Monochrome | - ///- /// Camera produces monochrome array with no Bayer encoding | - ///
| - /// 1 | - ///- /// Colour | - ///- /// Camera produces color image directly, requiring not Bayer decoding | - ///
| - /// 2 | - ///- /// RGGB | - ///- /// Camera produces RGGB encoded Bayer array images | - ///
| - /// 3 | - ///- /// CMYG | - ///- /// Camera produces CMYG encoded Bayer array images | - ///
| - /// 4 | - ///- /// CMYG2 | - ///- /// Camera produces CMYG2 encoded Bayer array images | - ///
| - /// 5 | - ///- /// LRGB | - ///- /// Camera produces Kodak TRUESENSE Bayer LRGB array images | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///
| - /// Y = 0 | - ///- /// R | - ///- /// G | - ///
| - /// Y = 1 | - ///- /// G | - ///- /// B | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///
| - /// Y = 0 | - ///- /// Y | - ///- /// C | - ///
| - /// Y = 1 | - ///- /// G | - ///- /// M | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///
| - /// Y = 0 | - ///- /// C | - ///- /// Y | - ///
| - /// Y = 1 | - ///- /// M | - ///- /// G | - ///
| - /// Y = 2 | - ///- /// C | - ///- /// Y | - ///
| - /// Y = 3 | - ///- /// G | - ///- /// M | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///- /// X = 2 | - ///- /// X = 3 | - ///
| - /// Y = 0 | - ///- /// L | - ///- /// R | - ///- /// L | - ///- /// G | - ///
| - /// Y = 1 | - ///- /// R | - ///- /// L | - ///- /// G | - ///- /// L | - ///
| - /// Y = 2 | - ///- /// L | - ///- /// G | - ///- /// L | - ///- /// B | - ///
| - /// Y = 3 | - ///- /// G | - ///- /// L | - ///- /// B | - ///- /// L | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///
| - /// Y = 0 | - ///- /// G | - ///- /// M | - ///
| - /// Y = 1 | - ///- /// C | - ///- /// Y | - ///
| - /// Y = 2 | - ///- /// M | - ///- /// G | - ///
| - /// Y = 3 | - ///- /// C | - ///- /// Y | - ///
OR
- /// OFFSETS INDEX MODE: Index into the Offsets array for the current camera offset - ///This is an optional property and can throw a NotImplementedException if Offset is not supported by the camera.
- /// The-
- ///
- OFFSET VALUE MODE - The
property is a direct numeric representation of the camera's offset. - /// -
- ///
- In this mode the
and properties must return integers specifying the valid range for
- /// - The
property must return a .
- ///
- /// - In this mode the
- OFFSETS INDEX MODE - The
property is the selected offset's index within the array of textual offset descriptions. - /// -
- ///
- In this mode the
method returns a 0-based array of strings, which describe available offset settings e.g. "ISO 200", "ISO 1600"
- /// and must throw s.
- /// - Please note that the
array is zero based.
- ///
- /// - In this mode the
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
must return the camera's highest valid setting.
- /// must be equal to or greater than .
- /// must throw a
- ///
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
must return the camera's lowest valid setting.
- /// must be less than or equal to .
- /// must throw a
- ///
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
- The
property must return a zero-based ArrayList of available offset setting names.
- /// - The
and properties must throw s.
- ///
This is an optional property and can throw a NotImplementedException.
- ///May throw a not implemented exception if CanAbortExpsoure is false.
- ///-
- ///
Must throw exception if camera is not idle and abort is unsuccessful (or not possible, e.g. during download).
- /// Must throw exception if hardware or communications error occurs.
- /// Must NOT throw an exception if the camera is already idle.
- ///
May throw a not implemented exception if this camera does not support PulseGuide
- ///-
- ///
guideNorth 0 North (+ declination/elevation)
- /// guideSouth 1 South (- declination/elevation)
- /// guideEast 2 East (+ right ascension/azimuth)
- /// guideWest 3 West (+ right ascension/azimuth)
- ///
Must be implemented, must not throw a NotImplementedException.
- ///May throw a not implemented exception
- ///This is a mandatory property and must not throw a
This is a mandatory property and must not throw a
Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- /// See the notes for theMust be implemented, must not throw a NotImplementedException.
- ///Slaved Read must be implemented and must not throw a NotImplementedException.
- ///Slaved Write can throw a NotImplementedException.
- /// Set this property to True to enable dome-telescope hardware slaving, if supported (seeSlewing must be implemented and must not throw a NotImplementedException.
- /// Raises an error ifMust be implemented, must not throw a NotImplementedException.
- /// Calling this method will immediately disable hardware slewing (Must be implemented, must not throw a NotImplementedException.
- /// For each valid slot number (from 0 to N-1), reports the focus offset for the given filter position. These values are focuser and filter dependent, and would usually be set up by the user via - /// the SetupDialog. The number of slots N can be determined from the length of the array. If focuser offsets are not available, then it should report back 0 for all array values. - ///Must be implemented, must not throw a NotImplementedException.
- /// For each valid slot number (from 0 to N-1), reports the name given to the filter position. These names would usually be set up by the user via the - /// SetupDialog. The number of slots N can be determined from the length of the array. If filter names are not available, then it should report back "Filter 1", "Filter 2", etc. - ///Must be implemented, must not throw a PropertyNotImplementedException.
- ///Must be implemented
Must be implemented
Must be implemented
- /// For most focusers this is the same as theMust be implemented
- /// The focuser can step between 0 andCan throw a not implemented exception
Valid only for absolute positioning focusers (see theCan throw a not implemented exception
Must throw an exception if the focuser does not intrinsically know what the step size is.TempComp Read must be implemented and must not throw a NotImplementedException.
- ///TempComp Write can throw a NotImplementedException.
- /// If theMust be implemented
- /// Will be True only if the focuser's temperature compensation can be turned on and off via theCan throw a not implemented exception
- /// Raises an exception if ambient temperature is not available. Commonly available on focusers with a built-in temperature compensation mode. - ///Can throw a not implemented exception
Some focusers may not support this function, in which case an exception will be raised. - ///Must be implemented
- ///Mandatory property, must be implemented, can NOT throw a NotImplementedException
- ///Optional property, can throw a NotImplementedException
- /// This property should return a value between 0.0 and 100.0 where 0.0 = clear sky and 100.0 = 100% cloud coverage - ///Optional property, can throw a NotImplementedException when the
Mandatory property, must NOT throw a NotImplementedException when the
Optional property, can throw a NotImplementedException when the
Mandatory property, must NOT throw a NotImplementedException when the
Optional property, can throw a NotImplementedException
- ///Optional property, can throw a NotImplementedException
- ///-
- ///
Light rain — when the precipitation rate is less than 2.5 mm (0.098 in) per hour
- /// Moderate rain — when the precipitation rate is between 2.5 mm (0.098 in) and 10 mm (0.39 in) per hour
- /// Heavy rain — when the precipitation rate is between 10 mm (0.39 in) and 50 mm (2.0 in) per hour
- /// Violent rain — when the precipitation rate is > 50 mm (2.0 in) per hour
- ///
Optional property, can throw a NotImplementedException
- /// This property returns the sky brightness measured in Lux. - ///-
- ///
0.0001 lux Moonless, overcast night sky (starlight)
- /// 0.002 lux Moonless clear night sky with airglow
- /// 0.27–1.0 lux Full moon on a clear night
- /// 3.4 lux Dark limit of civil twilight under a clear sky
- /// 50 lux Family living room lights (Australia, 1998)
- /// 80 lux Office building hallway/toilet lighting
- /// 100 lux Very dark overcast day
- /// 320–500 lux Office lighting
- /// 400 lux Sunrise or sunset on a clear day.
- /// 1000 lux Overcast day; typical TV studio lighting
- /// 10000–25000 lux Full daylight (not direct sun)
- /// 32000–100000 lux Direct sunlight
- ///
Optional property, can throw a NotImplementedException
- ///| - /// Sky Quality (mag/arcsec2) | - ///- /// Description | - ///
| - /// 22.0 | - ///- /// By convention, this is often assumed to be the average brightness of a moonless night sky that's completely free of artificial light pollution. | - ///
| - /// 21.0 | - ///- /// This is typical for a rural area with a medium-sized city not far away. It's comparable to the glow of the brightest section of the northern Milky Way, from Cygnus through Perseus. | - ///
| - /// 20.0 | - ///- /// This is typical for the outer suburbs of a major metropolis. The summer Milky Way is readily visible but severely washed out. | - ///
| - /// 19.0 | - ///- /// Typical for a suburb with widely spaced single-family homes. It's a little brighter than a remote rural site at the end of nautical twilight, when the Sun is 12° below the horizon. | - ///
| - /// 18.0 | - ///- /// Bright suburb or dark urban neighborhood. It's also a typical zenith skyglow at a rural site when the Moon is full. The Milky Way is invisible, or nearly so. | - ///
| - /// 17.0 | - ///- /// Typical near the center of a major city. | - ///
| - /// 13.0 | - ///- /// The zenith skyglow at the end of civil twilight, roughly a half hour after sunset, when the Sun is 6° below the horizon. Venus and Jupiter are easy to see, but bright stars are just beginning to appear. | - ///
| - /// 7.0 | - ///- /// The zenith skyglow at sunrise or sunset | - ///
Optional property, can throw a NotImplementedException
- ///Optional property, can throw a NotImplementedException
- ///Optional property, can throw a NotImplementedException
- ///Optional property, can throw a NotImplementedException
- /// The returned value must be between 0.0 and 360.0, interpreted according to the meteorological standard, where a special value of 0.0 is returned when the wind speed is 0.0. - /// Wind direction is measured clockwise from north, through east, where East=90.0, South=180.0, West=270.0 and North=360.0. - ///Optional property, can throw a NotImplementedException
- /// The units of this property are metres per second. Driver and application authors can use the ASCOM.Tools.Utilities.ConvertUnits method - /// to convert these units to and from miles per hour or knots. - ///Optional property, can throw a NotImplementedException
- /// The units of this property are metres per second. Driver and application authors can use the ASCOM.Tools.Utilities.ConvertUnits method - /// to convert these units to and from miles per hour or knots. - ///Must Not throw a NotImplementedException when the specified sensor Is implemented but must throw a NotImplementedException when the specified sensor Is Not implemented.
- ///Must Not throw a NotImplementedException when the specified sensor Is implemented - /// but must throw a NotImplementedException when the specified sensor Is Not implemented.
- ///Optional method, can throw a MethodNotImplementedException
- ///Must be implemented and must always return True for the IRotatorV3 interface or later.
- ///Must be implemented.
- ///Must be implemented.
- ///SPECIFICATION REVISION - IRotatorV3 - Platform 6.5
- ///Must be implemented.
- ///Optional - can throw a not implemented exception
- ///Must be implemented.
- ///Must be implemented.
- ///Introduced in IRotatorV3.
- /// Returns the mechanical position of the rotator, which is equivalent to the IRotatorV2Optional - can throw a not implemented exception
Must be implemented.
- ///Must be implemented.
- ///Must be implemented.
- ///Must be implemented.
- ///Introduced in IRotatorV3.
- /// Once this method has been called and the sync offset determined, both theMust be implemented and must not throw a NotImplementedException.
- ///Must be implemented, must not throw a
Devices are numbered from 0 to
Must be implemented, must not throw an ASCOM.NotImplementedException
- ///Can throw a
Must be implemented, must not throw an ASCOM.NotImplementedException
- ///Must be implemented, must not throw an ASCOM.NotImplementedException
- ///Must be implemented, must not throw a
-
- ///
Sets the device to a known state on connection
- /// Throws an until the client software has set the device state for the first time
- ///
Can throw a
Must be implemented, must not throw a
Must be implemented, must not throw a
Must be implemented, must not throw
Must be implemented, must not throw a
-
- ///
Sets the device to a known state on connection
- /// Throws an until the client software has set the device state for the first time
- ///
Can throw a
Must be implemented
This method must return an empty IList object if no actions are supported. Please do not throw aMust be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// This will always return False for mounts that do not have to be flipped. - /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// If this is true, theMust be implemented, must not throw a NotImplementedException.
- /// If this is true, theMust be implemented, must not throw a NotImplementedException.
- /// If this is true, theMust be implemented, must not throw a NotImplementedException.
- /// If this is true, theMust be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// If this is true, thenMust be implemented, must not throw a NotImplementedException.
- ///DeclinationRate Read must be implemented and must not throw a NotImplementedException.
- ///DeclinationRate Write can throw a NotImplementedException.
- /// This property, together with-
- ///
The property value represents an offset from zero motion.
- /// If is False, this property will always return 0.
- /// To discover whether this feature is supported, test the property.
- /// The supported range of this property is telescope specific, however, if this feature is supported, - /// it can be expected that the range is sufficient to allow correction of guiding errors caused by moderate misalignment - /// and periodic error.
- /// If this property is non-zero when an equatorial slew is initiated, the telescope should continue to update the slew - /// destination coordinates at the given offset rate.
- /// This will allow precise slews to a fast-moving target with a slow-slewing telescope.
- /// When the slew completes, the and properties should reflect the final (adjusted) destination.
- /// The units of this property are arcseconds per SI (atomic) second. Please note that for historic reasons the units of the property are seconds of RA per sidereal second.
- ///
-
- ///
If the driver does not know whether the attached telescope does its own refraction, and if the driver does not itself calculate - /// refraction, this property (if implemented) must raise an error when read.
- /// Writing to this property is optional. Often, a telescope (or its driver) calculates refraction using standard atmospheric parameters.
- /// If the client wishes to calculate a more accurate refraction, then this property could be set to False and these - /// client-refracted coordinates used.
- /// If disabling the telescope or driver's refraction is not supported, the driver must raise an error when an attempt to set - /// this property to False is made.
- /// Setting this property to True for a telescope or driver that does refraction, or to False for a telescope or driver that - /// does not do refraction, shall not raise an error. It shall have no effect.
- ///
Must be implemented, must not throw a NotImplementedException.
- /// Most amateur telescopes use topocentric coordinates. This coordinate system is simply the apparent position in the sky - /// (possibly uncorrected for atmospheric refraction) for "here and now", thus these are the coordinates that one would use with digital setting - /// circles and most amateur scopes. More sophisticated telescopes use one of the standard reference systems established by professional astronomers. - /// The most common is the Julian Epoch 2000 (J2000). These instruments apply corrections for precession,nutation, aberration, etc. to adjust the coordinates - /// from the standard system to the pointing direction for the time and location of "here and now". - ///-
- ///
To discover whether this feature is supported, test the property.
- /// The supported range of this property is telescope specific, however, if this feature is supported, it can be expected that the range is sufficient to - /// allow correction of guiding errors caused by moderate misalignment and periodic error.
- /// If a telescope does not support separate guiding rates in Right Ascension and Declination, then it is permissible for and GuideRateDeclination to be tied together. - /// In this case, changing one of the two properties will cause a change in the other.
- /// Mounts must start up with a known or default declination guide rate, and this property must return that known/default guide rate until changed.
- ///
-
- ///
To discover whether this feature is supported, test the property.
- /// The supported range of this property is telescope specific, however, if this feature is supported, it can be expected that the range is sufficient to allow correction of guiding errors caused by moderate - /// misalignment and periodic error.
- /// If a telescope does not support separate guiding rates in Right Ascension and Declination, then it is permissible for GuideRateRightAscension and to be tied together. - /// In this case, changing one of the two properties will cause a change in the other.
- /// Mounts must start up with a known or default right ascension guide rate, and this property must return that known/default guide rate until changed.
- ///
Must be implemented, must not throw a NotImplementedException.
- /// Reading the property will raise an error if the value is unavailable. - ///RightAscensionRate Read must be implemented and must not throw a NotImplementedException.
- ///RightAscensionRate Write can throw a NotImplementedException.
- /// This property, together with-
- ///
If this property is zero, tracking will be at the selected .
- /// If is False, this property must always return 0.
- /// To discover whether this feature is supported, test the The units of this property are seconds of right ascension per sidereal second. Please note that for historic reasons the units of the property are arcseconds per SI second.
- /// To convert a given rate in (the more common) units of sidereal seconds per UTC (clock) second, multiply the value by 0.9972695677 - /// (the number of UTC seconds in a sidereal second) then set the property. Please note that these units were chosen for the Telescope V1 standard, - /// and in retrospect, this was an unfortunate choice. However, to maintain backwards compatibility, the units cannot be changed. - /// A simple multiplication is all that's needed, as noted. The supported range of this property is telescope specific, however, - /// if this feature is supported, it can be expected that the range is sufficient to allow correction of guiding errors - /// caused by moderate misalignment and periodic error.
- /// If this property is non-zero when an equatorial slew is initiated, the telescope should continue to update the slew destination coordinates - /// at the given offset rate. This will allow precise slews to a fast-moving target with a slow-slewing telescope. When the slew completes, - /// the and properties should reflect the final (adjusted) destination. This is not a required - /// feature of this specification, however it is desirable.
- /// Use the property to enable and disable sidereal tracking (if supported).
- ///
-
- ///
Normal ( ) Where the mechanical Dec is in the range -90 deg to +90 deg
- /// Beyond the pole ( ) Where the mechanical Dec is in the range -180 deg to -90 deg or +90 deg to +180 deg.
- ///
-
- ///
HA_sky = HA_mech
- /// Dec_sky = Dec_mech
- ///
-
- ///
HA_sky = HA_mech + 12h, expressed in range ± 12h
- /// Dec_sky = 180d - Dec_mech, expressed in range ± 90d
- ///
-
- ///
pierEast Normal pointing state
- /// pierWest Beyond the pole pointing state
- ///
-
- ///
pierEast = abs(mechanical dec) <= 90 deg
- /// pierWest = abs(mechanical Dec) > 90 deg
- ///
Must be implemented, must not throw a NotImplementedException.
- /// It is required for a driver to calculate this from the system clock if the telescope - /// has no accessible source of sidereal time. Local Apparent Sidereal Time is the sidereal - /// time used for pointing telescopes, and thus must be calculated from the Greenwich Mean - /// Sidereal time, longitude, nutation in longitude and true ecliptic obliquity. - ///Tracking Read must be implemented and must not throw a NotImplementedException.
- ///Tracking Write can throw a NotImplementedException.
- /// Changing the value of this property will turn the sidereal drive on and off. - /// However, some telescopes may not support changing the value of this property - /// and thus may not support turning tracking on and off. - /// See theTrackingRate Read must be implemented and must not throw a NotImplementedException.
- ///TrackingRate Write can throw a NotImplementedException.
- /// Supported rates (one of theMust be implemented and must not throw a NotImplementedException.
- /// At a minimum, this must contain an item forUTCDate Read must be implemented and must not throw a NotImplementedException.
- ///UTCDate Write can throw a NotImplementedException.
- /// The driver must calculate this from the system clock if the telescope has no accessible source of UTC time. In this case, the property must not be writeable (this would change the system clock!) and will instead raise an error. - /// However, it is permitted to change the telescope's internal UTC clock if it is being used for this property. This allows clients to adjust the telescope's UTC clock as needed for accuracy. Reading the property - /// will raise an error if the value has never been set or is otherwise unavailable. - ///Must be implemented, must not throw a NotImplementedException.
- /// See the description ofMust be implemented, must not throw a NotImplementedException.
- /// This is only available for telescope Interface Versions 2 and later. - ///-
- ///
The movement rate must be within the value(s) obtained from a object in the - /// the collection. This is a signed value with negative rates moving in the opposite direction to positive rates.
- /// The values specified in are absolute, unsigned values and apply to both directions, determined by the sign used in this command.
- /// The value of must be True if the telescope is moving about any of its axes as a result of this method being called. - /// This can be used to simulate a handbox by initiating motion with the MouseDown event and stopping the motion with the MouseUp event.
- /// When the motion is stopped by setting the rate to zero the scope will be set to the previous or to no movement, depending on the state of the property.
- /// It may be possible to implement satellite tracking by using the method to move the scope in the required manner to track a satellite.
- ///
-
- ///
Raises an error if is true.
- /// The property must be True during pulse-guiding.
- /// The rate of motion for movements about the right ascension axis is - /// specified by the property. The rate of motion - /// for movements about the declination axis is specified by the - /// property. These two rates may be tied together - /// into a single rate, depending on the driver's implementation - /// and the capabilities of the telescope.
- ///
Deprecated for client applications.
- ///Deprecated for client applications.
- ///Deprecated for client applications.
- ///Must be implemented, must not throw an ASCOM.NotImplementedException.
- ///Must be implemented, must not throw an ASCOM.NotImplementedException.
- /// Returns one of the following status information: - ///-
- ///
0 CameraRunning The camera is running and video frames are available for viewing and recording
- /// 1 CameraRecording The camera is running and recording a video
- /// 2 CameraError Camera error condition serious enough to prevent further operations (connection fail, etc.).
- ///
Must be implemented, must not throw an ASCOM.NotImplementedException.
- ///Must be implemented, must not throw an ASCOM.NotImplementedException.
- /// This value is for information purposes only. The exposure cannot be set directly in seconds, useMust be implemented, must not throw an ASCOM.NotImplementedException.
- /// This value is for information purposes only. The exposure cannot be set directly in seconds, useMust be implemented, must not throw an ASCOM.NotImplementedException.
- /// Analogue cameras run in one of the two fixed frame rates - 25fps for PAL video and 29.97fps for NTSC video. - /// Digital cameras usually can run at a variable frame rate. This value is for information purposes only and cannot be set. The FrameRate has the same value during the entire operation of the device. - /// Changing the-
- ///
- Discrete gain video cameras will return a 0-based array of strings -
, which correspond to different discrete gain settings supported by the camera. must be set to an integer in this range. and must thrown an exception if - /// this mode is used.
- /// - Adjustable gain video cameras -
and return integers, which specify the valid range for .
- ///
-
- ///
- Discrete gamma video cameras will return a 0-based array of strings -
, which correspond to different discrete gamma settings supported by the camera. must be set to an integer in this range. and must thrown an exception if - /// this mode is used.
- /// - Adjustable gain video cameras -
and return integers, which specify the valid range for .
- ///
Must be implemented, must not throw an ASCOM.NotImplementedException.
- /// For analogue video cameras working via a frame grabber the dimensions of the video frames may be different than the dimension of the CCD chip - ///Must be implemented, must not throw an ASCOM.NotImplementedException.
- ///-
- ///
ICX285AL-F shall be reported as ICX285
- /// KAF-8300-AXC-CD-AA shall be reported as KAF-8300
- ///
Must be implemented, must not throw an ASCOM.NotImplementedException.
- ///| - /// Value | - ///- /// Enumeration | - ///- /// Meaning | - ///
| - /// 0 | - ///- /// Monochrome | - ///- /// Camera produces monochrome array with no Bayer encoding | - ///
| - /// 1 | - ///- /// Colour | - ///
- /// Camera produces color image directly, requiring not Bayer decoding. The monochrome pixels for the R, G and B channels are returned in this order in the |
- ///
| - /// 2 | - ///- /// RGGB | - ///- /// Camera produces RGGB encoded Bayer array images | - ///
| - /// 3 | - ///- /// CMYG | - ///- /// Camera produces CMYG encoded Bayer array images | - ///
| - /// 4 | - ///- /// CMYG2 | - ///- /// Camera produces CMYG2 encoded Bayer array images | - ///
| - /// 5 | - ///- /// LRGB | - ///- /// Camera produces Kodak TRUESENSE Bayer LRGB array images | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///
| - /// Y = 0 | - ///- /// R | - ///- /// G | - ///
| - /// Y = 1 | - ///- /// G | - ///- /// B | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///
| - /// Y = 0 | - ///- /// Y | - ///- /// C | - ///
| - /// Y = 1 | - ///- /// G | - ///- /// M | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///
| - /// Y = 0 | - ///- /// C | - ///- /// Y | - ///
| - /// Y = 1 | - ///- /// M | - ///- /// G | - ///
| - /// Y = 2 | - ///- /// C | - ///- /// Y | - ///
| - /// Y = 3 | - ///- /// G | - ///- /// M | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///- /// X = 2 | - ///- /// X = 3 | - ///
| - /// Y = 0 | - ///- /// L | - ///- /// R | - ///- /// L | - ///- /// G | - ///
| - /// Y = 1 | - ///- /// R | - ///- /// L | - ///- /// G | - ///- /// L | - ///
| - /// Y = 2 | - ///- /// L | - ///- /// G | - ///- /// L | - ///- /// B | - ///
| - /// Y = 3 | - ///- /// G | - ///- /// L | - ///- /// B | - ///- /// L | - ///
Must be implemented, must not throw an ASCOM.NotImplementedException.
- ///Must be implemented, must not throw an ASCOM.NotImplementedException.
When retrieving video frames using theMust be implemented, must not throw an ASCOM.NotImplementedException.
- /// For analogue video cameras working via a frame grabber the dimensions of the video frames may be different than the dimension of the CCD chip - ///Can throw a not implemented exception
- /// This method is intended for use in all current and future device types and to avoid name clashes, management of action names - /// is important from day 1. A two-part naming convention will be adopted - DeviceType:UniqueActionName where: - ///-
- ///
DeviceType is the string name of the device type e.g. Telescope, Camera, Switch etc.
- /// UniqueActionName is a single word, or multiple words joined by underscore characters, that sensibly describes the action to be performed.
- ///
May throw a NotImplementedException.
- ///May throw a NotImplementedException.
- ///May throw a NotImplementedException.
- ///Must be implemented
This method must return an emptyMay throw a not implemented exception if CanAbortExpsoure is false.
- ///-
- ///
Must throw exception if camera is not idle and abort is unsuccessful (or not possible, e.g. during download).
- /// Must throw exception if hardware or communications error occurs.
- /// Must NOT throw an exception if the camera is already idle.
- ///
-
- ///
0 CameraIdle At idle state, available to start exposure
- /// 1 CameraWaiting Exposure started but waiting (for shutter, trigger, filter wheel, etc.)
- /// 2 CameraExposing Exposure currently in progress
- /// 3 CameraReading CCD array is being read out (digitized)
- /// 4 CameraDownload Downloading data to PC
- /// 5 CameraError Camera error condition serious enough to prevent further operations (connection fail, etc.).
- ///
Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///May throw a not implemented exception if this camera does not support PulseGuide
- ///-
- ///
guideNorth 0 North (+ declination/elevation)
- /// guideSouth 1 South (- declination/elevation)
- /// guideEast 2 East (+ right ascension/azimuth)
- /// guideWest 3 West (+ right ascension/azimuth)
- ///
Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///May throw a not implemented exception
- ///Must be implemented by colour cameras, monochrome cameras must throw a NotImplementedException
- ///Must be implemented by colour cameras, monochrome cameras must throw a NotImplementedException
- ///Must be implemented, must not throw a NotImplementedException.
- /// It is recommended that this function be called only after aMust be implemented, must not throw a NotImplementedException.
- /// It is recommended that this function be called only after - /// aMust be implemented, must not throw a NotImplementedException.
- /// This must be a non-zero number representing the shortest possible exposure time supported by the camera model. - ///Must be implemented, must not throw a NotImplementedException.
- /// This can be used, for example, to specify the resolution of a user interface "spin control" used to dial in the exposure time. - ///Must throw a NotImplementedException if CanFastReadout is false or - /// return a boolean value if CanFastReadout is true.
- /// Must thrown an exception if noThis is an optional property and can throw a NotImplementedException if Gain is not supported by the camera.
- /// The-
- ///
- GAIN VALUE MODE - The
property is a direct numeric representation of the camera's gain. - /// -
- ///
- In this mode the
and properties must return integers specifying the valid range for
- /// - The
property must return a .
- ///
- /// - In this mode the
- GAINS INDEX MODE - The
property is the selected gain's index within the array of textual gain descriptions. - /// -
- ///
- In this mode the
method returns a 0-based array of strings, which describe available gain settings e.g. "ISO 200", "ISO 1600"
- /// and must throw s.
- /// - Please note that the
array is zero based.
- ///
- /// - In this mode the
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
must return the camera's highest valid setting.
- /// must be equal to or greater than .
- /// must throw a
- ///
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
must return the camera's lowest valid setting.
- /// must be less than or equal to .
- /// must throw a
- ///
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
- The
property must return a zero-based ArrayList of available gain setting names.
- /// - The
and properties must throw s.
- ///
May throw a NotImplementedException if PercentCompleted is not supported by the camera.
- /// If valid, returns an integer between 0 and 100, where 0 indicates 0% progress (function just started) and - /// 100 indicates 100% progress (i.e. completion). - ///Must be implemented if CanFastReadout is false, must throw a NotImplementedException if - /// CanFastReadout is true.
- ///Must be implemented if CanFastReadout is false, must throw a NotImplementedException if - /// CanFastReadout is true.
- /// This property provides an array of strings, each of which describes an available readout mode of the camera. - /// At least one string must be present in the list. The user interface of a control application will typically present to the - /// user a drop-list of modes. The choice of available modes made available is entirely at the discretion of the driver author. - /// Please note that if the camera has many different modes of operation, then the most commonly adjusted settings should be in - ///May throw a NotImplementedException if the sensor's name is not known.
- ///-
- ///
- All letters shall be upper-case. - ///
- Spaces shall not be included. - ///
- Any extra suffixes that define region codes, package types, temperature range, coatings, grading, colour/monochrome, - /// etc. shall not be included. - ///
- For colour sensors, if a suffix differentiates different Bayer matrix encodings, it shall be included. - ///
- The call shall return an empty string if the sensor name is not known. - ///
-
- ///
ICX285AL-F shall be reported as ICX285
- /// KAF-8300-AXC-CD-AA shall be reported as KAF-8300
- ///
May throw a NotImplementedException if the sensor type is not known.
- ///| - /// Value | - ///- /// Enumeration | - ///- /// Meaning | - ///
| - /// 0 | - ///- /// Monochrome | - ///- /// Camera produces monochrome array with no Bayer encoding | - ///
| - /// 1 | - ///- /// Colour | - ///- /// Camera produces color image directly, requiring not Bayer decoding | - ///
| - /// 2 | - ///- /// RGGB | - ///- /// Camera produces RGGB encoded Bayer array images | - ///
| - /// 3 | - ///- /// CMYG | - ///- /// Camera produces CMYG encoded Bayer array images | - ///
| - /// 4 | - ///- /// CMYG2 | - ///- /// Camera produces CMYG2 encoded Bayer array images | - ///
| - /// 5 | - ///- /// LRGB | - ///- /// Camera produces Kodak TRUESENSE Bayer LRGB array images | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///
| - /// Y = 0 | - ///- /// R | - ///- /// G | - ///
| - /// Y = 1 | - ///- /// G | - ///- /// B | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///
| - /// Y = 0 | - ///- /// Y | - ///- /// C | - ///
| - /// Y = 1 | - ///- /// G | - ///- /// M | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///
| - /// Y = 0 | - ///- /// C | - ///- /// Y | - ///
| - /// Y = 1 | - ///- /// M | - ///- /// G | - ///
| - /// Y = 2 | - ///- /// C | - ///- /// Y | - ///
| - /// Y = 3 | - ///- /// G | - ///- /// M | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///- /// X = 2 | - ///- /// X = 3 | - ///
| - /// Y = 0 | - ///- /// L | - ///- /// R | - ///- /// L | - ///- /// G | - ///
| - /// Y = 1 | - ///- /// R | - ///- /// L | - ///- /// G | - ///- /// L | - ///
| - /// Y = 2 | - ///- /// L | - ///- /// G | - ///- /// L | - ///- /// B | - ///
| - /// Y = 3 | - ///- /// G | - ///- /// L | - ///- /// B | - ///- /// L | - ///
| - /// | - ///- /// X = 0 | - ///- /// X = 1 | - ///
| - /// Y = 0 | - ///- /// G | - ///- /// M | - ///
| - /// Y = 1 | - ///- /// C | - ///- /// Y | - ///
| - /// Y = 2 | - ///- /// M | - ///- /// G | - ///
| - /// Y = 3 | - ///- /// C | - ///- /// Y | - ///
This is an optional property and can throw a NotImplementedException if Offset is not supported by the camera.
- /// The-
- ///
- OFFSET VALUE MODE - The
property is a direct numeric representation of the camera's offset. - /// -
- ///
- In this mode the
and properties must return integers specifying the valid range for
- /// - The
property must return a .
- ///
- /// - In this mode the
- OFFSETS INDEX MODE - The
property is the selected offset's index within the array of textual offset descriptions. - /// -
- ///
- In this mode the
method returns a 0-based array of strings, which describe available offset settings e.g. "ISO 200", "ISO 1600"
- /// and must throw s.
- /// - Please note that the
array is zero based.
- ///
- /// - In this mode the
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
must return the camera's highest valid setting.
- /// must be equal to or greater than .
- /// must throw a
- ///
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
must return the camera's lowest valid setting.
- /// must be less than or equal to .
- /// must throw a
- ///
This is an optional property and can throw a NotImplementedException.
- /// When-
- ///
- The
property must return a zero-based ArrayList of available offset setting names.
- /// - The
and properties must throw s.
- ///
This is an optional property and can throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- /// Calling this method will immediately disable hardware slewing (Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- /// See the notes for theMust be implemented, must not throw a NotImplementedException.
- ///Slaved Read must be implemented and must not throw a NotImplementedException.
- ///Slaved Write can throw a NotImplementedException.
- /// Set this property to True to enable dome-telescope hardware slaving, if supported (seeSlewing must be implemented and must not throw a NotImplementedException.
- /// Raises an error ifMust be implemented, must not throw a NotImplementedException.
- /// For each valid slot number (from 0 to N-1), reports the focus offset for the given filter position. These values are focuser and filter dependent, and would usually be set up by the user via - /// the SetupDialog. The number of slots N can be determined from the length of the array. If focuser offsets are not available, then it should report back 0 for all array values. - ///Must be implemented, must not throw a NotImplementedException.
- /// For each valid slot number (from 0 to N-1), reports the name given to the filter position. These names would usually be set up by the user via the - /// SetupDialog. The number of slots N can be determined from the length of the array. If filter names are not available, then it should report back "Filter 1", "Filter 2", etc. - ///Must be implemented, must not throw a NotImplementedException.
- /// Write a position number between 0 and N-1, where N is the number of filter slots (seeMust be implemented
Can throw a not implemented exception
Some focusers may not support this function, in which case an exception will be raised. - ///Must be implemented
Must be implemented
- /// For most focusers this is the same as theMust be implemented
- /// The focuser can step between 0 andMust be implemented
- ///Can throw a not implemented exception
Valid only for absolute positioning focusers (see theCan throw a not implemented exception
Must throw an exception if the focuser does not intrinsically know what the step size is.TempComp Read must be implemented and must not throw a NotImplementedException.
- ///TempComp Write can throw a NotImplementedException.
- /// If theMust be implemented
- /// Will be True only if the focuser's temperature compensation can be turned on and off via theCan throw a not implemented exception
- /// Raises an exception if ambient temperature is not available. Commonly available on focusers with a built-in temperature compensation mode. - ///Mandatory property, must be implemented, can NOT throw a NotImplementedException
- ///Optional property, can throw a NotImplementedException
- /// This property should return a value between 0.0 and 100.0 where 0.0 = clear sky and 100.0 = 100% cloud coverage - ///Optional property, can throw a NotImplementedException when the
Mandatory property, must NOT throw a NotImplementedException when the
Optional property, can throw a NotImplementedException when the
Mandatory property, must NOT throw a NotImplementedException when the
Optional property, can throw a NotImplementedException
- ///Optional property, can throw a NotImplementedException
- ///-
- ///
Light rain — when the precipitation rate is less than 2.5 mm (0.098 in) per hour
- /// Moderate rain — when the precipitation rate is between 2.5 mm (0.098 in) and 10 mm (0.39 in) per hour
- /// Heavy rain — when the precipitation rate is between 10 mm (0.39 in) and 50 mm (2.0 in) per hour
- /// Violent rain — when the precipitation rate is > 50 mm (2.0 in) per hour
- ///
Optional property, can throw a NotImplementedException
- /// This property returns the sky brightness measured in Lux. - ///-
- ///
0.0001 lux Moonless, overcast night sky (starlight)
- /// 0.002 lux Moonless clear night sky with airglow
- /// 0.27–1.0 lux Full moon on a clear night
- /// 3.4 lux Dark limit of civil twilight under a clear sky
- /// 50 lux Family living room lights (Australia, 1998)
- /// 80 lux Office building hallway/toilet lighting
- /// 100 lux Very dark overcast day
- /// 320–500 lux Office lighting
- /// 400 lux Sunrise or sunset on a clear day.
- /// 1000 lux Overcast day; typical TV studio lighting
- /// 10000–25000 lux Full daylight (not direct sun)
- /// 32000–100000 lux Direct sunlight
- ///
Optional property, can throw a NotImplementedException
- ///| - /// Sky Quality (mag/arcsec2) | - ///- /// Description | - ///
| - /// 22.0 | - ///- /// By convention, this is often assumed to be the average brightness of a moonless night sky that's completely free of artificial light pollution. | - ///
| - /// 21.0 | - ///- /// This is typical for a rural area with a medium-sized city not far away. It's comparable to the glow of the brightest section of the northern Milky Way, from Cygnus through Perseus. | - ///
| - /// 20.0 | - ///- /// This is typical for the outer suburbs of a major metropolis. The summer Milky Way is readily visible but severely washed out. | - ///
| - /// 19.0 | - ///- /// Typical for a suburb with widely spaced single-family homes. It's a little brighter than a remote rural site at the end of nautical twilight, when the Sun is 12° below the horizon. | - ///
| - /// 18.0 | - ///- /// Bright suburb or dark urban neighborhood. It's also a typical zenith skyglow at a rural site when the Moon is full. The Milky Way is invisible, or nearly so. | - ///
| - /// 17.0 | - ///- /// Typical near the center of a major city. | - ///
| - /// 13.0 | - ///- /// The zenith skyglow at the end of civil twilight, roughly a half hour after sunset, when the Sun is 6° below the horizon. Venus and Jupiter are easy to see, but bright stars are just beginning to appear. | - ///
| - /// 7.0 | - ///- /// The zenith skyglow at sunrise or sunset | - ///
Optional property, can throw a NotImplementedException
- ///Optional property, can throw a NotImplementedException
- ///Optional property, can throw a NotImplementedException
- ///Optional property, can throw a NotImplementedException
- /// The returned value must be between 0.0 and 360.0, interpreted according to the meteorological standard, where a special value of 0.0 is returned when the wind speed is 0.0. - /// Wind direction is measured clockwise from north, through east, where East=90.0, South=180.0, West=270.0 and North=360.0. - ///Optional property, can throw a NotImplementedException
- /// The units of this property are metres per second. Driver and application authors can use the ASCOM.Tools.Utilities.ConvertUnits method - /// to convert these units to and from miles per hour or knots. - ///Optional property, can throw a NotImplementedException
- /// The units of this property are metres per second. Driver and application authors can use the ASCOM.Tools.Utilities.ConvertUnits method - /// to convert these units to and from miles per hour or knots. - ///Must Not throw a NotImplementedException when the specified sensor Is implemented but must throw a NotImplementedException when the specified sensor Is Not implemented.
- ///Must Not throw a NotImplementedException when the specified sensor Is implemented - /// but must throw a NotImplementedException when the specified sensor Is Not implemented.
- ///Optional method, can throw a NotImplementedException
- ///Must be implemented and must always return True for the IRotatorV3 interface or later.
- ///Optional - can throw a not implemented exception
Must be implemented.
- ///Must be implemented.
- ///Must be implemented.
- ///SPECIFICATION REVISION - IRotatorV3 - Platform 6.5
- ///Must be implemented.
- ///SPECIFICATION REVISION - IRotatorV3 - Platform 6.5
- ///Must be implemented.
- ///Optional - can throw a not implemented exception
- ///Must be implemented.
- ///Must be implemented.
- ///Introduced in IRotatorV3.
- /// Returns the mechanical position of the rotator, which is equivalent to the IRotatorV2Must be implemented.
- ///Introduced in IRotatorV3.
- /// Once this method has been called and the sync offset determined, both theMust be implemented.
- ///Introduced in IRotatorV3.
- ///Must be implemented and must not throw a NotImplementedException.
- ///Must be implemented, must not throw a
Devices are numbered from 0 to
Must be implemented, must not throw an ASCOM.NotImplementedException
- ///Can throw a
Must be implemented, must not throw an ASCOM.NotImplementedException
- ///Must be implemented, must not throw an ASCOM.NotImplementedException
- ///Must be implemented, must not throw a
-
- ///
Sets the device to a known state on connection
- /// Throws an until the client software has set the device state for the first time
- ///
Can throw a
Must be implemented, must not throw a
Must be implemented, must not throw a
Must be implemented, must not throw
Must be implemented, must not throw a
-
- ///
Sets the device to a known state on connection
- /// Throws an until the client software has set the device state for the first time
- ///
Can throw a
This is an optional method and can throw a
This is an optional method and can throw a
This is an optional method and can throw a
This is a mandatory method and must not throw a
This is a mandatory method and must not throw a
This is an optional method and can throw a
Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- ///Must be implemented, must not throw a NotImplementedException.
- /// See the description ofMust be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// This is only available for telescope Interface Versions 2 and later. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// This will always return False for mounts that do not have to be flipped. - /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// If this is true, theMust be implemented, must not throw a NotImplementedException.
- /// If this is true, theMust be implemented, must not throw a NotImplementedException.
- /// If this is true, theMust be implemented, must not throw a NotImplementedException.
- /// If this is true, theMust be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// May raise an error if the telescope is not connected. - ///Must be implemented, must not throw a NotImplementedException.
- /// If this is true, thenMust be implemented, must not throw a NotImplementedException.
- ///DeclinationRate Read must be implemented and must not throw a NotImplementedException.
- ///DeclinationRate Write can throw a NotImplementedException.
- /// This property, together with-
- ///
The property value represents an offset from zero motion.
- /// If is False, this property will always return 0.
- /// To discover whether this feature is supported, test the property.
- /// The supported range of this property is telescope specific, however, if this feature is supported, - /// it can be expected that the range is sufficient to allow correction of guiding errors caused by moderate misalignment - /// and periodic error.
- /// If this property is non-zero when an equatorial slew is initiated, the telescope should continue to update the slew - /// destination coordinates at the given offset rate.
- /// This will allow precise slews to a fast-moving target with a slow-slewing telescope.
- /// When the slew completes, the and properties should reflect the final (adjusted) destination.
- /// The units of this property are arcseconds per SI (atomic) second. Please note that for historic reasons the units of the property are seconds of RA per sidereal second.
- ///
-
- ///
If the driver does not know whether the attached telescope does its own refraction, and if the driver does not itself calculate - /// refraction, this property (if implemented) must raise an error when read.
- /// Writing to this property is optional. Often, a telescope (or its driver) calculates refraction using standard atmospheric parameters.
- /// If the client wishes to calculate a more accurate refraction, then this property could be set to False and these - /// client-refracted coordinates used.
- /// If disabling the telescope or driver's refraction is not supported, the driver must raise an error when an attempt to set - /// this property to False is made.
- /// Setting this property to True for a telescope or driver that does refraction, or to False for a telescope or driver that - /// does not do refraction, shall not raise an error. It shall have no effect.
- ///
Must be implemented, must not throw a NotImplementedException.
- /// Most amateur telescopes use topocentric coordinates. This coordinate system is simply the apparent position in the sky - /// (possibly uncorrected for atmospheric refraction) for "here and now", thus these are the coordinates that one would use with digital setting - /// circles and most amateur scopes. More sophisticated telescopes use one of the standard reference systems established by professional astronomers. - /// The most common is the Julian Epoch 2000 (J2000). These instruments apply corrections for precession,nutation, aberration, etc. to adjust the coordinates - /// from the standard system to the pointing direction for the time and location of "here and now". - ///-
- ///
To discover whether this feature is supported, test the property.
- /// The supported range of this property is telescope specific, however, if this feature is supported, it can be expected that the range is sufficient to - /// allow correction of guiding errors caused by moderate misalignment and periodic error.
- /// If a telescope does not support separate guiding rates in Right Ascension and Declination, then it is permissible for and GuideRateDeclination to be tied together. - /// In this case, changing one of the two properties will cause a change in the other.
- /// Mounts must start up with a known or default declination guide rate, and this property must return that known/default guide rate until changed.
- ///
-
- ///
To discover whether this feature is supported, test the property.
- /// The supported range of this property is telescope specific, however, if this feature is supported, it can be expected that the range is sufficient to allow correction of guiding errors caused by moderate - /// misalignment and periodic error.
- /// If a telescope does not support separate guiding rates in Right Ascension and Declination, then it is permissible for GuideRateRightAscension and to be tied together. - /// In this case, changing one of the two properties will cause a change in the other.
- /// Mounts must start up with a known or default right ascension guide rate, and this property must return that known/default guide rate until changed.
- ///
-
- ///
The movement rate must be within the value(s) obtained from a object in the - /// the collection. This is a signed value with negative rates moving in the opposite direction to positive rates.
- /// The values specified in are absolute, unsigned values and apply to both directions, determined by the sign used in this command.
- /// The value of must be True if the telescope is moving about any of its axes as a result of this method being called. - /// This can be used to simulate a handbox by initiating motion with the MouseDown event and stopping the motion with the MouseUp event.
- /// When the motion is stopped by setting the rate to zero the scope will be set to the previous or to no movement, depending on the state of the property.
- /// It may be possible to implement satellite tracking by using the method to move the scope in the required manner to track a satellite.
- ///
-
- ///
Raises an error if is true.
- /// The property must be True during pulse-guiding.
- /// The rate of motion for movements about the right ascension axis is - /// specified by the property. The rate of motion - /// for movements about the declination axis is specified by the - /// property. These two rates may be tied together - /// into a single rate, depending on the driver's implementation - /// and the capabilities of the telescope.
- ///
Must be implemented, must not throw a NotImplementedException.
- /// Reading the property will raise an error if the value is unavailable. - ///RightAscensionRate Read must be implemented and must not throw a NotImplementedException.
- ///RightAscensionRate Write can throw a NotImplementedException.
- /// This property, together with-
- ///
If this property is zero, tracking will be at the selected .
- /// If is False, this property must always return 0.
- /// To discover whether this feature is supported, test the The units of this property are seconds of right ascension per sidereal second. Please note that for historic reasons the units of the property are arcseconds per SI second.
- /// To convert a given rate in (the more common) units of sidereal seconds per UTC (clock) second, multiply the value by 0.9972695677 - /// (the number of UTC seconds in a sidereal second) then set the property. Please note that these units were chosen for the Telescope V1 standard, - /// and in retrospect, this was an unfortunate choice. However, to maintain backwards compatibility, the units cannot be changed. - /// A simple multiplication is all that's needed, as noted. The supported range of this property is telescope specific, however, - /// if this feature is supported, it can be expected that the range is sufficient to allow correction of guiding errors - /// caused by moderate misalignment and periodic error.
- /// If this property is non-zero when an equatorial slew is initiated, the telescope should continue to update the slew destination coordinates - /// at the given offset rate. This will allow precise slews to a fast-moving target with a slow-slewing telescope. When the slew completes, - /// the and properties should reflect the final (adjusted) destination. This is not a required - /// feature of this specification, however it is desirable.
- /// Use the property to enable and disable sidereal tracking (if supported).
- ///
-
- ///
Normal ( ) Where the mechanical Dec is in the range -90 deg to +90 deg
- /// Beyond the pole ( ) Where the mechanical Dec is in the range -180 deg to -90 deg or +90 deg to +180 deg.
- ///
-
- ///
HA_sky = HA_mech
- /// Dec_sky = Dec_mech
- ///
-
- ///
HA_sky = HA_mech + 12h, expressed in range ± 12h
- /// Dec_sky = 180d - Dec_mech, expressed in range ± 90d
- ///
-
- ///
pierEast Normal pointing state
- /// pierWest Beyond the pole pointing state
- ///
-
- ///
pierEast = abs(mechanical dec) <= 90 deg
- /// pierWest = abs(mechanical Dec) > 90 deg
- ///
Must be implemented, must not throw a NotImplementedException.
- /// It is required for a driver to calculate this from the system clock if the telescope - /// has no accessible source of sidereal time. Local Apparent Sidereal Time is the sidereal - /// time used for pointing telescopes, and thus must be calculated from the Greenwich Mean - /// Sidereal time, longitude, nutation in longitude and true ecliptic obliquity. - ///Deprecated for client applications.
- ///Deprecated for client applications.
- ///Deprecated for client applications.
- ///Tracking Read must be implemented and must not throw a NotImplementedException.
- ///Tracking Write can throw a NotImplementedException.
- /// Changing the value of this property will turn the sidereal drive on and off. - /// However, some telescopes may not support changing the value of this property - /// and thus may not support turning tracking on and off. - /// See theTrackingRate Read must be implemented and must not throw a NotImplementedException.
- ///TrackingRate Write can throw a NotImplementedException.
- /// Supported rates (one of theMust be implemented and must not throw a NotImplementedException.
- /// At a minimum, this must contain an item forUTCDate Read must be implemented and must not throw a NotImplementedException.
- ///UTCDate Write can throw a NotImplementedException.
- /// The driver must calculate this from the system clock if the telescope has no accessible source of UTC time. In this case, the property must not be writeable (this would change the system clock!) and will instead raise an error. - /// However, it is permitted to change the telescope's internal UTC clock if it is being used for this property. This allows clients to adjust the telescope's UTC clock as needed for accuracy. Reading the property - /// will raise an error if the value has never been set or is otherwise unavailable. - ///-
-
- using ASCOM.Com;
- using ASCOM.Common;
-
- namespace StandAloneChooser
- {
- internal class Program
- {
- static void Main(string[] args)
- {
- // Create a stand alone Chooser instance that is configured to display Camera devices
- ChooserSA chooser = new()
- {
- DeviceType = ASCOM.Common.DeviceTypes.Camera
- };
-
- // Present a Chooser dialogue with e Platform Camera simulator pre-selected
- string progId = chooser.Choose("ASCOM.Simulator.Camera");
-
- // List the driver that the user chose
- Console.WriteLine($"The user selected this ProgID: {progId}");
-
- // Illustrate the Library extension method for converting a string device type name to a DeviceTypes enum value
- const string DEVICE_TYPE_NAME = "ObservingConditions";
- DeviceTypes deviceType = DEVICE_TYPE_NAME.ToDeviceType();
- Console.WriteLine($"The DeviceTypes enum value of the string device type name: {DEVICE_TYPE_NAME} is: {deviceType}");
-
- // Illustrate the Library extension method for converting a DeviceTypes enum value to a string device type name
- string deviceTypeString = deviceType.ToDeviceString();
- Console.WriteLine($"The DeviceTypes enum value of the string device type name: {deviceType} is: {deviceTypeString}");
-
- // Wait for a key press before closing the program
- Console.ReadKey();
- }
- }
- }
-
- -
-
-
-
-
-
-
-
-
+
-
+
-
+
-
-
-
-
-
-
-
-
-
+
-
+
-
+
-
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
-
+
-
+
-
+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+ ///
The result is computed even if any of the range checks fail.
+ /// Negative ideg, iamin and/or asec produce a warning status, but the absolute value is used in the conversion.
+ /// If there are multiple errors, the status value reflects only the first, the smallest taking precedence.
+ ///
-
+ ///
Star data for an epoch other than J2000.0 (for example from the Hipparcos catalog, which has an epoch of J1991.25) will require a preliminary call to iauPmsafe before use.
+ /// The proper motion in RA is dRA/dt rather than cos(Dec)*dRA/dt.
+ /// The TDB date date1+date2 is a Julian Date, apportioned in any convenient way between the two arguments. For example, JD(TDB)=2450123.8g could be expressed in any of these ways, among others: + /// + ///
+ ///+ /// + /// + /// + /// + ///+ /// Date 1 + ///+ /// Date 2 + ///+ /// Method + ///+ /// + ///+ /// 2450123.8 + ///+ /// 0.0 + ///+ /// JD method + ///+ /// + ///+ /// 2451545.0 + ///+ /// -1421.3 + ///+ /// J2000 method + ///+ /// + ///+ /// 2400000.5 + ///+ /// 50123.2 + ///+ /// MJD method + ///+ /// + ///+ /// 2450123.5 + ///+ /// 0.2 + ///+ /// Date and time method + ///The JD method is the most natural and convenient to use in cases where the loss of several decimal digits of resolution is acceptable. The J2000 method is best matched to the way the argument is handled internally + /// and will deliver the optimum resolution. The MJD method and the date and time methods are both good compromises between resolution and convenience. For most applications of this function the choice will not be at all critical. + ///TT can be used instead of TDB without any significant impact on accuracy. + ///
+ /// The available accuracy is better than 1 milliarcsecond, limited mainly by the precession-nutation model that is used, namely IAU 2000A/2006. Very close to solar system bodies, additional + /// errors of up to several milliarcseconds can occur because of unmodelled light deflection; however, the Sun's contribution is taken into account, to first order.The accuracy limitations of + /// the SOFA function iauEpv00 (used to compute Earth position and velocity) can contribute aberration errors of up to 5 microarcseconds. Light deflection at the Sun's limb is uncertain at the 0.4 mas level.
+ /// Should the transformation to (equinox based) apparent place be required rather than (CIO based) intermediate place, subtract the equation of the origins from the returned right ascension: + /// RA = RI - EO. (The Anp function can then be applied, as required, to keep the result in the conventional 0-2pi range.)
+ ///
-
+ ///
Star data for an epoch other than J2000.0 (for example from the Hipparcos catalog, which has an epoch of J1991.25) will require a preliminary call to iauPmsafe before use.
+ /// The proper motion in RA is dRA/dt rather than cos(Dec)*dRA/dt.
+ /// utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day. + /// However, JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the length is 86399, 86400 or 86401 SI seconds. + ///Applications should use the function iauDtf2d to convert from calendar date and time of day into 2-part quasi Julian Date, as it implements the leap-second-ambiguity convention just described.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// UT1-UTC is tabulated in IERS bulletins. It increases by exactly one second at the end of each positive UTC leap second, introduced in order to keep UT1-UTC within +/- 0.9s. n.b. This practice is under review, and in the future UT1-UTC may grow essentially without limit.
+ /// The geographical coordinates are with respect to the WGS84 reference ellipsoid. TAKE CARE WITH THE LONGITUDE SIGN: the longitude required by the present function is east-positive (i.e. right-handed), in accordance with geographical convention.
+ /// The polar motion xp,yp can be obtained from IERS bulletins. The values are the coordinates (in radians) of the Celestial Intermediate Pole with respect to the International Terrestrial Reference System (see IERS Conventions 2003), measured along the meridians 0 and 90 deg west respectively. For many applications, xp and yp can be set to zero.
+ /// If hm, the height above the ellipsoid of the observing station in meters, is not known but phpa, the pressure in hPa (=mB), is available, an adequate estimate of hm can be obtained from the expression: + /// hm = -29.3 * tsl * log ( phpa / 1013.25 );
+ ///where tsl is the approximate sea-level air temperature in K (See Astrophysical Quantities, C.W.Allen, 3rd edition, section 52). Similarly, if the pressure phpa is not known, it can be estimated from the height of the observing station, hm, as follows: + ///phpa = 1013.25 * exp ( -hm / ( 29.3 * tsl ) );
+ ///Note, however, that the refraction is nearly proportional to the pressure and that an accurate phpa value is important for precise work.
+ /// The argument wl specifies the observing wavelength in micrometers. The transition from optical to radio is assumed to occur at 100 micrometers (about 3000 GHz).
+ /// The accuracy of the result is limited by the corrections for refraction, which use a simple A*tan(z) + B*tan^3(z) model. Providing the meteorological parameters are known accurately and there are no gross local effects, the predicted observed coordinates should be within 0.05 arcsec (optical) or 1 arcsec (radio) for a zenith distance of less than 70 degrees, better than 30 arcsec (optical or radio) at 85 degrees and better than 20 arcmin (optical) or 30 arcmin (radio) at the horizon. + /// Without refraction, the complementary functions iauAtco13 and iauAtoc13 are self-consistent to better than 1 microarcsecond all over the celestial sphere. With refraction included, consistency falls off at high zenith distances, but is still better than 0.05 arcsec at 85 degrees.
+ /// "Observed" Az,ZD means the position that would be seen by a perfect geodetically aligned theodolite. (Zenith distance is used rather than altitude in order to reflect the fact that no allowance is made for depression of the horizon.) This is related to the observed HA,Dec via the standard rotation, using the geodetic latitude (corrected for polar motion), while the observed HA and RA are related simply through the Earth rotation angle and the site longitude. "Observed" RA,Dec or HA,Dec thus means the position that would be seen by a perfect equatorial with its polar axis aligned to the Earth's axis of rotation.
+ /// It is advisable to take great care with units, as even unlikely values of the input parameters are accepted and processed in accordance with the models used.
+ ///
-
+ ///
The TDB date date1+date2 is a Julian Date, apportioned in any convenient way between the two arguments. For example, JD(TDB)=2450123.8g could be expressed in any of these ways, among others: + /// + ///
+ ///+ /// + /// + /// + /// + ///+ /// Date 1 + ///+ /// Date 2 + ///+ /// Method + ///+ /// + ///+ /// 2450123.8 + ///+ /// 0.0 + ///+ /// JD method + ///+ /// + ///+ /// 2451545.0 + ///+ /// -1421.3 + ///+ /// J2000 method + ///+ /// + ///+ /// 2400000.5 + ///+ /// 50123.2 + ///+ /// MJD method + ///+ /// + ///+ /// 2450123.5 + ///+ /// 0.2 + ///+ /// Date and time method + ///The JD method is the most natural and convenient to use in cases where the loss of several decimal digits of resolution is acceptable. The J2000 method is best matched to the way the argument is handled internally + /// and will deliver the optimum resolution. The MJD method and the date and time methods are both good compromises between resolution and convenience. For most applications of this function the choice will not be at all critical. + ///TT can be used instead of TDB without any significant impact on accuracy. + ///
+ /// Iterative techniques are used for the aberration and light deflection corrections so that the functions Atic13 and Atci13 are accurate inverses; + /// even at the edge of the Sun's disk the discrepancy is only about 1 nanoarcsecond.
+ /// The available accuracy is better than 1 milliarcsecond, limited mainly by the precession-nutation model that is used, namely IAU 2000A/2006. Very close to solar system bodies, additional + /// errors of up to several milliarcseconds can occur because of unmodelled light deflection; however, the Sun's contribution is taken into account, to first order.The accuracy limitations of + /// the SOFA function iauEpv00 (used to compute Earth position and velocity) can contribute aberration errors of up to 5 microarcseconds. Light deflection at the Sun's limb is uncertain at the 0.4 mas level.
+ /// Should the transformation to (equinox based) J2000.0 mean place be required rather than (CIO based) ICRS coordinates, subtract the equation of the origins from the returned right ascension: + /// RA = RI - EO. (The Anp function can then be applied, as required, to keep the result in the conventional 0-2pi range.)
+ ///
-
+ ///
utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day. + /// However, JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the length is 86399, 86400 or 86401 SI seconds. + ///Applications should use the function iauDtf2d to convert from calendar date and time of day into 2-part quasi Julian Date, as it implements the leap-second-ambiguity convention just described.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// UT1-UTC is tabulated in IERS bulletins. It increases by exactly one second at the end of each positive UTC leap second, introduced in order to keep UT1-UTC within +/- 0.9s. n.b. This practice is under review, and in the future UT1-UTC may grow essentially without limit.
+ /// The geographical coordinates are with respect to the WGS84 reference ellipsoid. TAKE CARE WITH THE LONGITUDE SIGN: the longitude required by the present function is east-positive (i.e. right-handed), in accordance with geographical convention.
+ /// The polar motion xp,yp can be obtained from IERS bulletins. The values are the coordinates (in radians) of the Celestial Intermediate Pole with respect to the International Terrestrial + /// Reference System (see IERS Conventions 2003), measured along the meridians 0 and 90 deg west respectively. For many applications, xp and yp can be set to zero.
+ /// If hm, the height above the ellipsoid of the observing station in meters, is not known but phpa, the pressure in hPa (=mB), is available, an adequate estimate of hm can be obtained from the expression: + /// hm = -29.3 * tsl * log ( phpa / 1013.25 );
+ ///where tsl is the approximate sea-level air temperature in K (See Astrophysical Quantities, C.W.Allen, 3rd edition, section 52). Similarly, if the pressure phpa is not known, it can be estimated from the height of the observing station, hm, as follows: + ///phpa = 1013.25 * exp ( -hm / ( 29.3 * tsl ) );
+ ///Note, however, that the refraction is nearly proportional to the pressure and that an accurate phpa value is important for precise work.
+ /// The argument wl specifies the observing wavelength in micrometers. The transition from optical to radio is assumed to occur at 100 micrometers (about 3000 GHz).
+ /// "Observed" Az,ZD means the position that would be seen by a perfect geodetically aligned theodolite. (Zenith distance is used rather than altitude in order to reflect the fact that no + /// allowance is made for depression of the horizon.) This is related to the observed HA,Dec via the standard rotation, using the geodetic latitude (corrected for polar motion), while the observed HA and RA are related simply through the Earth rotation + /// angle and the site longitude. "Observed" RA,Dec or HA,Dec thus means the position that would be seen by a perfect equatorial with its polar axis aligned to the Earth's axis of rotation.
+ /// The accuracy of the result is limited by the corrections for refraction, which use a simple A*tan(z) + B*tan^3(z) model. Providing the meteorological parameters are known accurately and there are no gross local effects, the predicted astrometric + /// coordinates should be within 0.05 arcsec (optical) or 1 arcsec (radio) for a zenith distance of less than 70 degrees, better than 30 arcsec (optical or radio) at 85 degrees and better than 20 arcmin (optical) or 30 arcmin (radio) at the horizon.
+ /// The complementary functions iauAtio13 and iauAtoi13 are self-consistent to better than 1 microarcsecond all over the celestial sphere.
+ /// It is advisable to take great care with units, as even unlikely values of the input parameters are accepted and processed in accordance with the models used.
+ ///
-
+ ///
"Observed" Az,ZD means the position that would be seen by a perfect geodetically aligned theodolite. (Zenith distance is used rather than altitude in order to reflect the fact that no + /// allowance is made for depression of the horizon.) This is related to the observed HA,Dec via the standard rotation, using the geodetic latitude (corrected for polar motion), while the + /// observed HA and RA are related simply through the Earth rotation angle and the site longitude. "Observed" RA,Dec or HA,Dec thus means the position that would be seen by a perfect equatorial with its polar axis aligned to the Earth's axis of rotation.
+ /// Only the first character of the type argument is significant. "R" or "r" indicates that ob1 and ob2 are the observed right ascension and declination; "H" or "h" indicates that they are hour angle (west +ve) and declination; anything else ("A" or + /// "a" is recommended) indicates that ob1 and ob2 are azimuth (north zero, east 90 deg) and zenith distance.
+ /// utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day. + /// However, JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the length is 86399, 86400 or 86401 SI seconds. + ///Applications should use the function iauDtf2d to convert from calendar date and time of day into 2-part quasi Julian Date, as it implements the leap-second-ambiguity convention just described.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// UT1-UTC is tabulated in IERS bulletins. It increases by exactly one second at the end of each positive UTC leap second, introduced in order to keep UT1-UTC within +/- 0.9s. n.b. This practice is under review, and in the future UT1-UTC may grow essentially without limit.
+ /// The geographical coordinates are with respect to the WGS84 reference ellipsoid. TAKE CARE WITH THE LONGITUDE SIGN: the longitude required by the present function is east-positive (i.e. right-handed), in accordance with geographical convention.
+ /// The polar motion xp,yp can be obtained from IERS bulletins. The values are the coordinates (in radians) of the Celestial Intermediate Pole with respect to the International Terrestrial Reference System (see IERS Conventions 2003), measured along the + /// meridians 0 and 90 deg west respectively. For many applications, xp and yp can be set to zero.
+ /// If hm, the height above the ellipsoid of the observing station in meters, is not known but phpa, the pressure in hPa (=mB), is available, an adequate estimate of hm can be obtained from the expression: + /// hm = -29.3 * tsl * log ( phpa / 1013.25 );
+ ///where tsl is the approximate sea-level air temperature in K (See Astrophysical Quantities, C.W.Allen, 3rd edition, section 52). Similarly, if the pressure phpa is not known, it can be estimated from the height of the observing station, hm, as follows: + ///phpa = 1013.25 * exp ( -hm / ( 29.3 * tsl ) );
+ ///Note, however, that the refraction is nearly proportional to the pressure and that an accurate phpa value is important for precise work.
+ /// The argument wl specifies the observing wavelength in micrometers. The transition from optical to radio is assumed to occur at 100 micrometers (about 3000 GHz).
+ /// The accuracy of the result is limited by the corrections for refraction, which use a simple A*tan(z) + B*tan^3(z) model. Providing the meteorological parameters are known accurately and + /// there are no gross local effects, the predicted astrometric coordinates should be within 0.05 arcsec (optical) or 1 arcsec (radio) for a zenith distance of less than 70 degrees, better than 30 arcsec (optical or radio) at 85 degrees and better + /// than 20 arcmin (optical) or 30 arcmin (radio) at the horizon. + /// Without refraction, the complementary functions iauAtco13 and iauAtoc13 are self-consistent to better than 1 microarcsecond all over the celestial sphere. With refraction included, consistency falls off at high zenith distances, but is still better than 0.05 arcsec at 85 degrees.
+ /// It is advisable to take great care with units, as even unlikely values of the input parameters are accepted and processed in accordance with the models used.
+ ///
-
+ ///
"Observed" Az,ZD means the position that would be seen by a perfect geodetically aligned theodolite. (Zenith distance is used rather than altitude in order to reflect the fact that no + /// allowance is made for depression of the horizon.) This is related to the observed HA,Dec via the standard rotation, using the geodetic latitude (corrected for polar motion), while the + /// observed HA and RA are related simply through the Earth rotation angle and the site longitude. "Observed" RA,Dec or HA,Dec thus means the position that would be seen by a perfect equatorial + /// with its polar axis aligned to the Earth's axis of rotation.
+ /// Only the first character of the type argument is significant. "R" or "r" indicates that ob1 and ob2 are the observed right ascension and declination; "H" or "h" indicates that they are + /// hour angle (west +ve) and declination; anything else ("A" or "a" is recommended) indicates that ob1 and ob2 are azimuth (north zero, east 90 deg) and zenith distance.
+ /// utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day. + /// However, JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the length is 86399, 86400 or 86401 SI seconds. + ///Applications should use the function iauDtf2d to convert from calendar date and time of day into 2-part quasi Julian Date, as it implements the leap-second-ambiguity convention just described.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// UT1-UTC is tabulated in IERS bulletins. It increases by exactly one second at the end of each positive UTC leap second, introduced in order to keep UT1-UTC within +/- 0.9s. n.b. This + /// practice is under review, and in the future UT1-UTC may grow essentially without limit.
+ /// The geographical coordinates are with respect to the WGS84 reference ellipsoid. TAKE CARE WITH THE LONGITUDE SIGN: the longitude required by the present function is east-positive + /// (i.e. right-handed), in accordance with geographical convention.
+ /// The polar motion xp,yp can be obtained from IERS bulletins. The values are the coordinates (in radians) of the Celestial Intermediate Pole with respect to the International Terrestrial + /// Reference System (see IERS Conventions 2003), measured along the meridians 0 and 90 deg west respectively. For many applications, xp and yp can be set to zero.
+ /// If hm, the height above the ellipsoid of the observing station in meters, is not known but phpa, the pressure in hPa (=mB), is available, an adequate estimate of hm can be obtained from the expression: + /// hm = -29.3 * tsl * log ( phpa / 1013.25 );
+ ///where tsl is the approximate sea-level air temperature in K (See Astrophysical Quantities, C.W.Allen, 3rd edition, section 52). Similarly, if the pressure phpa is not known, it can be estimated from the height of the observing station, hm, as follows: + ///phpa = 1013.25 * exp ( -hm / ( 29.3 * tsl ) );
+ ///Note, however, that the refraction is nearly proportional to the pressure and that an accurate phpa value is important for precise work.
+ /// The argument wl specifies the observing wavelength in micrometers. The transition from optical to radio is assumed to occur at 100 micrometers (about 3000 GHz).
+ /// The accuracy of the result is limited by the corrections for refraction, which use a simple A*tan(z) + B*tan^3(z) model. Providing the meteorological parameters are known accurately and + /// there are no gross local effects, the predicted astrometric coordinates should be within 0.05 arcsec (optical) or 1 arcsec (radio) for a zenith distance of less than 70 degrees, better + /// than 30 arcsec (optical or radio) at 85 degrees and better than 20 arcmin (optical) or 30 arcmin (radio) at the horizon. + /// Without refraction, the complementary functions iauAtio13 and iauAtoi13 are self-consistent to better than 1 microarcsecond all over the celestial sphere. With refraction included, + /// consistency falls off at high zenith distances, but is still better than 0.05 arcsec at 85 degrees.
+ /// It is advisable to take great care with units, as even unlikely values of the input parameters are accepted and processed in accordance with the models used.
+ ///
-
+ ///
Scale identifies the time scale. Only the value "UTC" (in upper case) is significant, and enables handling of leap seconds (see Note 4).
+ /// For calendar conventions and limitations, see iauCal2jd.
+ /// The sum of the results, d1+d2, is Julian Date, where normally d1 is the Julian Day Number and d2 is the fraction of a day. In the case of UTC, where the use of JD is problematical, special conventions apply: see the next note.
+ /// JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The SOFA internal convention is that the quasi-JD day represents UTC days whether the length is 86399, + /// 86400 or 86401 SI seconds. In the 1960-1972 era there were smaller jumps (in either direction) each time the linear UTC(TAI) expression was changed, and these "mini-leaps" are also included in the SOFA convention.
+ /// The warning status "time is after end of day" usually means that the sec argument is greater than 60.0. However, in a day ending in a leap second the limit changes to 61.0 (or 59.0 in the case of a negative leap second).
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// Only in the case of continuous and regular time scales (TAI, TT, TCG, TCB and TDB) is the result d1+d2 a Julian Date, strictly speaking. In the other cases (UT1 and UTC) the result must be + /// used with circumspection; in particular the difference between two such results cannot be interpreted as a precise time interval.
+ ///
-
+ ///
The TT date date1+date2 is a Julian Date, apportioned in any convenient way between the two arguments. For example, JD(TT)=2450123.7 could be expressed in any of these ways, among others: + /// + ///
+ ///+ /// + /// + /// + /// + ///+ /// Date 1 + ///+ /// Date 2 + ///+ /// Method + ///+ /// + ///+ /// 2450123.7 + ///+ /// 0.0 + ///+ /// JD method + ///+ /// + ///+ /// 2451545.0 + ///+ /// -1421.3 + ///+ /// J2000 method + ///+ /// + ///+ /// 2400000.5 + ///+ /// 50123.2 + ///+ /// MJD method + ///+ /// + ///+ /// 2450123.5 + ///+ /// 0.2 + ///+ /// Date and time method + ///The JD method is the most natural and convenient to use in cases where the loss of several decimal digits of resolution is acceptable. The J2000 method is best matched to the way the argument is handled internally + /// and will deliver the optimum resolution. The MJD method and the date and time methods are both good compromises between resolution and convenience. For most applications of this function the choice will not be at all critical. + ///
+ /// The equation of the origins is the distance between the true equinox and the celestial intermediate origin and, equivalently, the difference between Earth rotation angle and Greenwich + /// apparent sidereal time (ERA-GST). It comprises the precession (since J2000.0) in right ascension plus the equation of the equinoxes (including the small correction terms).
+ ///
-
+ ///
tai1+tai2 is Julian Date, apportioned in any convenient way between the two arguments, for example where tai1 is the Julian Day Number and tai2 is the fraction of a day. The returned + /// tt1,tt2 follow suit.
+ ///
-
+ ///
tai1+tai2 is Julian Date, apportioned in any convenient way between the two arguments, for example where tai1 is the Julian Day Number and tai2 is the fraction of a day. The returned utc1 + /// and utc2 form an analogous pair, except that a special convention is used, to deal with the problem of leap seconds - see the next note.
+ /// JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the + /// length is 86399, 86400 or 86401 SI seconds. In the 1960-1972 era there were smaller jumps (in either direction) each time the linear UTC(TAI) expression was changed, and these "mini-leaps are also included in the SOFA convention.
+ /// The function iauD2dtf can be used to transform the UTC quasi-JD into calendar date and clock time, including UTC leap second handling.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ ///
-
+ ///
The result is computed even if any of the range checks fail.
+ /// Negative ihour, imin and/or sec produce a warning status, but the absolute value is used in the conversion.
+ /// If there are multiple errors, the status value reflects only the first, the smallest taking precedence.
+ ///
-
+ ///
tt1+tt2 is Julian Date, apportioned in any convenient way between the two arguments, for example where tt1 is the Julian Day Number and tt2 is the fraction of a day. The returned tai1,tai2 follow suit.
+ ///
-
+ ///
utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day.
+ /// JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the + /// length is 86399, 86400 or 86401 SI seconds. In the 1960-1972 era there were smaller jumps (in either direction) each time the linear UTC(TAI) expression was changed, and these "mini-leaps" are also included in the SOFA convention.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// The function iauDtf2d converts from calendar date and time of day into 2-part Julian Date, and in the case of UTC implements the leap-second-ambiguity convention described above.
+ /// The returned TAI1,TAI2 are such that their sum is the TAI Julian Date.
+ ///
-
+ ///
The result is computed even if any of the range checks fail.
+ /// Negative ideg, iamin and/or asec produce a warning status, but the absolute value is used in the conversion.
+ /// If there are multiple errors, the status value reflects only the first, the smallest taking precedence.
+ ///
-
+ ///
The result is computed even if any of the range checks fail.
+ /// Negative ideg, iamin and/or asec produce a warning status, but the absolute value is used in the conversion.
+ /// If there are multiple errors, the status value reflects only the first, the smallest taking precedence.
+ ///
-
+ ///
Star data for an epoch other than J2000.0 (for example from the Hipparcos catalog, which has an epoch of J1991.25) will require a preliminary call to iauPmsafe before use.
+ /// The proper motion in RA is dRA/dt rather than cos(Dec)*dRA/dt.
+ /// The TDB date date1+date2 is a Julian Date, apportioned in any convenient way between the two arguments. For example, JD(TDB)=2450123.8g could be expressed in any of these ways, among others: + /// + ///
+ ///+ /// + /// + /// + /// + ///+ /// Date 1 + ///+ /// Date 2 + ///+ /// Method + ///+ /// + ///+ /// 2450123.8 + ///+ /// 0.0 + ///+ /// JD method + ///+ /// + ///+ /// 2451545.0 + ///+ /// -1421.3 + ///+ /// J2000 method + ///+ /// + ///+ /// 2400000.5 + ///+ /// 50123.2 + ///+ /// MJD method + ///+ /// + ///+ /// 2450123.5 + ///+ /// 0.2 + ///+ /// Date and time method + ///The JD method is the most natural and convenient to use in cases where the loss of several decimal digits of resolution is acceptable. The J2000 method is best matched to the way the argument is handled internally + /// and will deliver the optimum resolution. The MJD method and the date and time methods are both good compromises between resolution and convenience. For most applications of this function the choice will not be at all critical. + ///TT can be used instead of TDB without any significant impact on accuracy. + ///
+ /// The available accuracy is better than 1 milliarcsecond, limited mainly by the precession-nutation model that is used, namely IAU 2000A/2006. Very close to solar system bodies, additional + /// errors of up to several milliarcseconds can occur because of unmodelled light deflection; however, the Sun's contribution is taken into account, to first order.The accuracy limitations of + /// the SOFA function iauEpv00 (used to compute Earth position and velocity) can contribute aberration errors of up to 5 microarcseconds. Light deflection at the Sun's limb is uncertain at the 0.4 mas level.
+ /// Should the transformation to (equinox based) apparent place be required rather than (CIO based) intermediate place, subtract the equation of the origins from the returned right ascension: + /// RA = RI - EO. (The Anp function can then be applied, as required, to keep the result in the conventional 0-2pi range.)
+ ///
-
+ ///
Star data for an epoch other than J2000.0 (for example from the Hipparcos catalog, which has an epoch of J1991.25) will require a preliminary call to iauPmsafe before use.
+ /// The proper motion in RA is dRA/dt rather than cos(Dec)*dRA/dt.
+ /// The TDB date date1+date2 is a Julian Date, apportioned in any convenient way between the two arguments. For example, JD(TDB)=2450123.8g could be expressed in any of these ways, among others: + /// + ///
+ ///+ /// + /// + /// + /// + ///+ /// Date 1 + ///+ /// Date 2 + ///+ /// Method + ///+ /// + ///+ /// 2450123.8 + ///+ /// 0.0 + ///+ /// JD method + ///+ /// + ///+ /// 2451545.0 + ///+ /// -1421.3 + ///+ /// J2000 method + ///+ /// + ///+ /// 2400000.5 + ///+ /// 50123.2 + ///+ /// MJD method + ///+ /// + ///+ /// 2450123.5 + ///+ /// 0.2 + ///+ /// Date and time method + ///The JD method is the most natural and convenient to use in cases where the loss of several decimal digits of resolution is acceptable. The J2000 method is best matched to the way the argument is handled internally + /// and will deliver the optimum resolution. The MJD method and the date and time methods are both good compromises between resolution and convenience. For most applications of this function the choice will not be at all critical. + ///TT can be used instead of TDB without any significant impact on accuracy. + ///
+ /// The available accuracy is better than 1 milliarcsecond, limited mainly by the precession-nutation model that is used, namely IAU 2000A/2006. Very close to solar system bodies, additional + /// errors of up to several milliarcseconds can occur because of unmodelled light deflection; however, the Sun's contribution is taken into account, to first order.The accuracy limitations of + /// the SOFA function iauEpv00 (used to compute Earth position and velocity) can contribute aberration errors of up to 5 microarcseconds. Light deflection at the Sun's limb is uncertain at the 0.4 mas level.
+ /// Should the transformation to (equinox based) apparent place be required rather than (CIO based) intermediate place, subtract the equation of the origins from the returned right ascension: + /// RA = RI - EO. (The Anp function can then be applied, as required, to keep the result in the conventional 0-2pi range.)
+ ///
-
+ ///
Star data for an epoch other than J2000.0 (for example from the Hipparcos catalog, which has an epoch of J1991.25) will require a preliminary call to iauPmsafe before use.
+ /// The proper motion in RA is dRA/dt rather than cos(Dec)*dRA/dt.
+ /// utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day. + /// However, JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the length is 86399, 86400 or 86401 SI seconds. + ///Applications should use the function iauDtf2d to convert from calendar date and time of day into 2-part quasi Julian Date, as it implements the leap-second-ambiguity convention just described.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// UT1-UTC is tabulated in IERS bulletins. It increases by exactly one second at the end of each positive UTC leap second, introduced in order to keep UT1-UTC within +/- 0.9s. n.b. This practice is under review, and in the future UT1-UTC may grow essentially without limit.
+ /// The geographical coordinates are with respect to the WGS84 reference ellipsoid. TAKE CARE WITH THE LONGITUDE SIGN: the longitude required by the present function is east-positive (i.e. right-handed), in accordance with geographical convention.
+ /// The polar motion xp,yp can be obtained from IERS bulletins. The values are the coordinates (in radians) of the Celestial Intermediate Pole with respect to the International Terrestrial Reference System (see IERS Conventions 2003), measured along the meridians 0 and 90 deg west respectively. For many applications, xp and yp can be set to zero.
+ /// If hm, the height above the ellipsoid of the observing station in meters, is not known but phpa, the pressure in hPa (=mB), is available, an adequate estimate of hm can be obtained from the expression: + /// hm = -29.3 * tsl * log ( phpa / 1013.25 );
+ ///where tsl is the approximate sea-level air temperature in K (See Astrophysical Quantities, C.W.Allen, 3rd edition, section 52). Similarly, if the pressure phpa is not known, it can be estimated from the height of the observing station, hm, as follows: + ///phpa = 1013.25 * exp ( -hm / ( 29.3 * tsl ) );
+ ///Note, however, that the refraction is nearly proportional to the pressure and that an accurate phpa value is important for precise work.
+ /// The argument wl specifies the observing wavelength in micrometers. The transition from optical to radio is assumed to occur at 100 micrometers (about 3000 GHz).
+ /// The accuracy of the result is limited by the corrections for refraction, which use a simple A*tan(z) + B*tan^3(z) model. Providing the meteorological parameters are known accurately and there are no gross local effects, the predicted observed coordinates should be within 0.05 arcsec (optical) or 1 arcsec (radio) for a zenith distance of less than 70 degrees, better than 30 arcsec (optical or radio) at 85 degrees and better than 20 arcmin (optical) or 30 arcmin (radio) at the horizon. + /// Without refraction, the complementary functions iauiauAtco13 (P/Invoke internal) and iauAtoc13 are self-consistent to better than 1 microarcsecond all over the celestial sphere. With refraction included, consistency falls off at high zenith distances, but is still better than 0.05 arcsec at 85 degrees.
+ /// "Observed" Az,ZD means the position that would be seen by a perfect geodetically aligned theodolite. (Zenith distance is used rather than altitude in order to reflect the fact that no allowance is made for depression of the horizon.) This is related to the observed HA,Dec via the standard rotation, using the geodetic latitude (corrected for polar motion), while the observed HA and RA are related simply through the Earth rotation angle and the site longitude. "Observed" RA,Dec or HA,Dec thus means the position that would be seen by a perfect equatorial with its polar axis aligned to the Earth's axis of rotation.
+ /// It is advisable to take great care with units, as even unlikely values of the input parameters are accepted and processed in accordance with the models used.
+ ///
-
+ ///
Star data for an epoch other than J2000.0 (for example from the Hipparcos catalog, which has an epoch of J1991.25) will require a preliminary call to iauPmsafe before use.
+ /// The proper motion in RA is dRA/dt rather than cos(Dec)*dRA/dt.
+ /// utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day. + /// However, JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the length is 86399, 86400 or 86401 SI seconds. + ///Applications should use the function iauDtf2d to convert from calendar date and time of day into 2-part quasi Julian Date, as it implements the leap-second-ambiguity convention just described.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// UT1-UTC is tabulated in IERS bulletins. It increases by exactly one second at the end of each positive UTC leap second, introduced in order to keep UT1-UTC within +/- 0.9s. n.b. This practice is under review, and in the future UT1-UTC may grow essentially without limit.
+ /// The geographical coordinates are with respect to the WGS84 reference ellipsoid. TAKE CARE WITH THE LONGITUDE SIGN: the longitude required by the present function is east-positive (i.e. right-handed), in accordance with geographical convention.
+ /// The polar motion xp,yp can be obtained from IERS bulletins. The values are the coordinates (in radians) of the Celestial Intermediate Pole with respect to the International Terrestrial Reference System (see IERS Conventions 2003), measured along the meridians 0 and 90 deg west respectively. For many applications, xp and yp can be set to zero.
+ /// If hm, the height above the ellipsoid of the observing station in meters, is not known but phpa, the pressure in hPa (=mB), is available, an adequate estimate of hm can be obtained from the expression: + /// hm = -29.3 * tsl * log ( phpa / 1013.25 );
+ ///where tsl is the approximate sea-level air temperature in K (See Astrophysical Quantities, C.W.Allen, 3rd edition, section 52). Similarly, if the pressure phpa is not known, it can be estimated from the height of the observing station, hm, as follows: + ///phpa = 1013.25 * exp ( -hm / ( 29.3 * tsl ) );
+ ///Note, however, that the refraction is nearly proportional to the pressure and that an accurate phpa value is important for precise work.
+ /// The argument wl specifies the observing wavelength in micrometers. The transition from optical to radio is assumed to occur at 100 micrometers (about 3000 GHz).
+ /// The accuracy of the result is limited by the corrections for refraction, which use a simple A*tan(z) + B*tan^3(z) model. Providing the meteorological parameters are known accurately and there are no gross local effects, the predicted observed coordinates should be within 0.05 arcsec (optical) or 1 arcsec (radio) for a zenith distance of less than 70 degrees, better than 30 arcsec (optical or radio) at 85 degrees and better than 20 arcmin (optical) or 30 arcmin (radio) at the horizon. + /// Without refraction, the complementary functions iauAtco13 and iauAtoc13 are self-consistent to better than 1 microarcsecond all over the celestial sphere. With refraction included, consistency falls off at high zenith distances, but is still better than 0.05 arcsec at 85 degrees.
+ /// "Observed" Az,ZD means the position that would be seen by a perfect geodetically aligned theodolite. (Zenith distance is used rather than altitude in order to reflect the fact that no allowance is made for depression of the horizon.) This is related to the observed HA,Dec via the standard rotation, using the geodetic latitude (corrected for polar motion), while the observed HA and RA are related simply through the Earth rotation angle and the site longitude. "Observed" RA,Dec or HA,Dec thus means the position that would be seen by a perfect equatorial with its polar axis aligned to the Earth's axis of rotation.
+ /// It is advisable to take great care with units, as even unlikely values of the input parameters are accepted and processed in accordance with the models used.
+ ///
-
+ ///
The TDB date date1+date2 is a Julian Date, apportioned in any convenient way between the two arguments. For example, JD(TDB)=2450123.8g could be expressed in any of these ways, among others: + /// + ///
+ ///+ /// + /// + /// + /// + ///+ /// Date 1 + ///+ /// Date 2 + ///+ /// Method + ///+ /// + ///+ /// 2450123.8 + ///+ /// 0.0 + ///+ /// JD method + ///+ /// + ///+ /// 2451545.0 + ///+ /// -1421.3 + ///+ /// J2000 method + ///+ /// + ///+ /// 2400000.5 + ///+ /// 50123.2 + ///+ /// MJD method + ///+ /// + ///+ /// 2450123.5 + ///+ /// 0.2 + ///+ /// Date and time method + ///The JD method is the most natural and convenient to use in cases where the loss of several decimal digits of resolution is acceptable. The J2000 method is best matched to the way the argument is handled internally + /// and will deliver the optimum resolution. The MJD method and the date and time methods are both good compromises between resolution and convenience. For most applications of this function the choice will not be at all critical. + ///TT can be used instead of TDB without any significant impact on accuracy. + ///
+ /// Iterative techniques are used for the aberration and light deflection corrections so that the functions iauAtic13 (P/Invoke internal) and Atci13 are accurate inverses; + /// even at the edge of the Sun's disk the discrepancy is only about 1 nanoarcsecond.
+ /// The available accuracy is better than 1 milliarcsecond, limited mainly by the precession-nutation model that is used, namely IAU 2000A/2006. Very close to solar system bodies, additional + /// errors of up to several milliarcseconds can occur because of unmodelled light deflection; however, the Sun's contribution is taken into account, to first order.The accuracy limitations of + /// the SOFA function iauEpv00 (used to compute Earth position and velocity) can contribute aberration errors of up to 5 microarcseconds. Light deflection at the Sun's limb is uncertain at the 0.4 mas level.
+ /// Should the transformation to (equinox based) J2000.0 mean place be required rather than (CIO based) ICRS coordinates, subtract the equation of the origins from the returned right ascension: + /// RA = RI - EO. (The Anp function can then be applied, as required, to keep the result in the conventional 0-2pi range.)
+ ///
-
+ ///
The TDB date date1+date2 is a Julian Date, apportioned in any convenient way between the two arguments. For example, JD(TDB)=2450123.8g could be expressed in any of these ways, among others: + /// + ///
+ ///+ /// + /// + /// + /// + ///+ /// Date 1 + ///+ /// Date 2 + ///+ /// Method + ///+ /// + ///+ /// 2450123.8 + ///+ /// 0.0 + ///+ /// JD method + ///+ /// + ///+ /// 2451545.0 + ///+ /// -1421.3 + ///+ /// J2000 method + ///+ /// + ///+ /// 2400000.5 + ///+ /// 50123.2 + ///+ /// MJD method + ///+ /// + ///+ /// 2450123.5 + ///+ /// 0.2 + ///+ /// Date and time method + ///The JD method is the most natural and convenient to use in cases where the loss of several decimal digits of resolution is acceptable. The J2000 method is best matched to the way the argument is handled internally + /// and will deliver the optimum resolution. The MJD method and the date and time methods are both good compromises between resolution and convenience. For most applications of this function the choice will not be at all critical. + ///TT can be used instead of TDB without any significant impact on accuracy. + ///
+ /// Iterative techniques are used for the aberration and light deflection corrections so that the functions Atic13 and Atci13 are accurate inverses; + /// even at the edge of the Sun's disk the discrepancy is only about 1 nanoarcsecond.
+ /// The available accuracy is better than 1 milliarcsecond, limited mainly by the precession-nutation model that is used, namely IAU 2000A/2006. Very close to solar system bodies, additional + /// errors of up to several milliarcseconds can occur because of unmodelled light deflection; however, the Sun's contribution is taken into account, to first order.The accuracy limitations of + /// the SOFA function iauEpv00 (used to compute Earth position and velocity) can contribute aberration errors of up to 5 microarcseconds. Light deflection at the Sun's limb is uncertain at the 0.4 mas level.
+ /// Should the transformation to (equinox based) J2000.0 mean place be required rather than (CIO based) ICRS coordinates, subtract the equation of the origins from the returned right ascension: + /// RA = RI - EO. (The Anp function can then be applied, as required, to keep the result in the conventional 0-2pi range.)
+ ///
-
+ ///
utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day. + /// However, JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the length is 86399, 86400 or 86401 SI seconds. + ///Applications should use the function iauDtf2d to convert from calendar date and time of day into 2-part quasi Julian Date, as it implements the leap-second-ambiguity convention just described.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// UT1-UTC is tabulated in IERS bulletins. It increases by exactly one second at the end of each positive UTC leap second, introduced in order to keep UT1-UTC within +/- 0.9s. n.b. This practice is under review, and in the future UT1-UTC may grow essentially without limit.
+ /// The geographical coordinates are with respect to the WGS84 reference ellipsoid. TAKE CARE WITH THE LONGITUDE SIGN: the longitude required by the present function is east-positive (i.e. right-handed), in accordance with geographical convention.
+ /// The polar motion xp,yp can be obtained from IERS bulletins. The values are the coordinates (in radians) of the Celestial Intermediate Pole with respect to the International Terrestrial + /// Reference System (see IERS Conventions 2003), measured along the meridians 0 and 90 deg west respectively. For many applications, xp and yp can be set to zero.
+ /// If hm, the height above the ellipsoid of the observing station in meters, is not known but phpa, the pressure in hPa (=mB), is available, an adequate estimate of hm can be obtained from the expression: + /// hm = -29.3 * tsl * log ( phpa / 1013.25 );
+ ///where tsl is the approximate sea-level air temperature in K (See Astrophysical Quantities, C.W.Allen, 3rd edition, section 52). Similarly, if the pressure phpa is not known, it can be estimated from the height of the observing station, hm, as follows: + ///phpa = 1013.25 * exp ( -hm / ( 29.3 * tsl ) );
+ ///Note, however, that the refraction is nearly proportional to the pressure and that an accurate phpa value is important for precise work.
+ /// The argument wl specifies the observing wavelength in micrometers. The transition from optical to radio is assumed to occur at 100 micrometers (about 3000 GHz).
+ /// "Observed" Az,ZD means the position that would be seen by a perfect geodetically aligned theodolite. (Zenith distance is used rather than altitude in order to reflect the fact that no + /// allowance is made for depression of the horizon.) This is related to the observed HA,Dec via the standard rotation, using the geodetic latitude (corrected for polar motion), while the observed HA and RA are related simply through the Earth rotation + /// angle and the site longitude. "Observed" RA,Dec or HA,Dec thus means the position that would be seen by a perfect equatorial with its polar axis aligned to the Earth's axis of rotation.
+ /// The accuracy of the result is limited by the corrections for refraction, which use a simple A*tan(z) + B*tan^3(z) model. Providing the meteorological parameters are known accurately and there are no gross local effects, the predicted astrometric + /// coordinates should be within 0.05 arcsec (optical) or 1 arcsec (radio) for a zenith distance of less than 70 degrees, better than 30 arcsec (optical or radio) at 85 degrees and better than 20 arcmin (optical) or 30 arcmin (radio) at the horizon.
+ /// The complementary functions iauiauAtio13 (P/Invoke internal) and iauAtoi13 are self-consistent to better than 1 microarcsecond all over the celestial sphere.
+ /// It is advisable to take great care with units, as even unlikely values of the input parameters are accepted and processed in accordance with the models used.
+ ///
-
+ ///
utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day. + /// However, JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the length is 86399, 86400 or 86401 SI seconds. + ///Applications should use the function iauDtf2d to convert from calendar date and time of day into 2-part quasi Julian Date, as it implements the leap-second-ambiguity convention just described.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// UT1-UTC is tabulated in IERS bulletins. It increases by exactly one second at the end of each positive UTC leap second, introduced in order to keep UT1-UTC within +/- 0.9s. n.b. This practice is under review, and in the future UT1-UTC may grow essentially without limit.
+ /// The geographical coordinates are with respect to the WGS84 reference ellipsoid. TAKE CARE WITH THE LONGITUDE SIGN: the longitude required by the present function is east-positive (i.e. right-handed), in accordance with geographical convention.
+ /// The polar motion xp,yp can be obtained from IERS bulletins. The values are the coordinates (in radians) of the Celestial Intermediate Pole with respect to the International Terrestrial + /// Reference System (see IERS Conventions 2003), measured along the meridians 0 and 90 deg west respectively. For many applications, xp and yp can be set to zero.
+ /// If hm, the height above the ellipsoid of the observing station in meters, is not known but phpa, the pressure in hPa (=mB), is available, an adequate estimate of hm can be obtained from the expression: + /// hm = -29.3 * tsl * log ( phpa / 1013.25 );
+ ///where tsl is the approximate sea-level air temperature in K (See Astrophysical Quantities, C.W.Allen, 3rd edition, section 52). Similarly, if the pressure phpa is not known, it can be estimated from the height of the observing station, hm, as follows: + ///phpa = 1013.25 * exp ( -hm / ( 29.3 * tsl ) );
+ ///Note, however, that the refraction is nearly proportional to the pressure and that an accurate phpa value is important for precise work.
+ /// The argument wl specifies the observing wavelength in micrometers. The transition from optical to radio is assumed to occur at 100 micrometers (about 3000 GHz).
+ /// "Observed" Az,ZD means the position that would be seen by a perfect geodetically aligned theodolite. (Zenith distance is used rather than altitude in order to reflect the fact that no + /// allowance is made for depression of the horizon.) This is related to the observed HA,Dec via the standard rotation, using the geodetic latitude (corrected for polar motion), while the observed HA and RA are related simply through the Earth rotation + /// angle and the site longitude. "Observed" RA,Dec or HA,Dec thus means the position that would be seen by a perfect equatorial with its polar axis aligned to the Earth's axis of rotation.
+ /// The accuracy of the result is limited by the corrections for refraction, which use a simple A*tan(z) + B*tan^3(z) model. Providing the meteorological parameters are known accurately and there are no gross local effects, the predicted astrometric + /// coordinates should be within 0.05 arcsec (optical) or 1 arcsec (radio) for a zenith distance of less than 70 degrees, better than 30 arcsec (optical or radio) at 85 degrees and better than 20 arcmin (optical) or 30 arcmin (radio) at the horizon.
+ /// The complementary functions iauAtio13 and iauAtoi13 are self-consistent to better than 1 microarcsecond all over the celestial sphere.
+ /// It is advisable to take great care with units, as even unlikely values of the input parameters are accepted and processed in accordance with the models used.
+ ///
-
+ ///
"Observed" Az,ZD means the position that would be seen by a perfect geodetically aligned theodolite. (Zenith distance is used rather than altitude in order to reflect the fact that no + /// allowance is made for depression of the horizon.) This is related to the observed HA,Dec via the standard rotation, using the geodetic latitude (corrected for polar motion), while the + /// observed HA and RA are related simply through the Earth rotation angle and the site longitude. "Observed" RA,Dec or HA,Dec thus means the position that would be seen by a perfect equatorial with its polar axis aligned to the Earth's axis of rotation.
+ /// Only the first character of the type argument is significant. "R" or "r" indicates that ob1 and ob2 are the observed right ascension and declination; "H" or "h" indicates that they are hour angle (west +ve) and declination; anything else ("A" or + /// "a" is recommended) indicates that ob1 and ob2 are azimuth (north zero, east 90 deg) and zenith distance.
+ /// utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day. + /// However, JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the length is 86399, 86400 or 86401 SI seconds. + ///Applications should use the function iauDtf2d to convert from calendar date and time of day into 2-part quasi Julian Date, as it implements the leap-second-ambiguity convention just described.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// UT1-UTC is tabulated in IERS bulletins. It increases by exactly one second at the end of each positive UTC leap second, introduced in order to keep UT1-UTC within +/- 0.9s. n.b. This practice is under review, and in the future UT1-UTC may grow essentially without limit.
+ /// The geographical coordinates are with respect to the WGS84 reference ellipsoid. TAKE CARE WITH THE LONGITUDE SIGN: the longitude required by the present function is east-positive (i.e. right-handed), in accordance with geographical convention.
+ /// The polar motion xp,yp can be obtained from IERS bulletins. The values are the coordinates (in radians) of the Celestial Intermediate Pole with respect to the International Terrestrial Reference System (see IERS Conventions 2003), measured along the + /// meridians 0 and 90 deg west respectively. For many applications, xp and yp can be set to zero.
+ /// If hm, the height above the ellipsoid of the observing station in meters, is not known but phpa, the pressure in hPa (=mB), is available, an adequate estimate of hm can be obtained from the expression: + /// hm = -29.3 * tsl * log ( phpa / 1013.25 );
+ ///where tsl is the approximate sea-level air temperature in K (See Astrophysical Quantities, C.W.Allen, 3rd edition, section 52). Similarly, if the pressure phpa is not known, it can be estimated from the height of the observing station, hm, as follows: + ///phpa = 1013.25 * exp ( -hm / ( 29.3 * tsl ) );
+ ///Note, however, that the refraction is nearly proportional to the pressure and that an accurate phpa value is important for precise work.
+ /// The argument wl specifies the observing wavelength in micrometers. The transition from optical to radio is assumed to occur at 100 micrometers (about 3000 GHz).
+ /// The accuracy of the result is limited by the corrections for refraction, which use a simple A*tan(z) + B*tan^3(z) model. Providing the meteorological parameters are known accurately and + /// there are no gross local effects, the predicted astrometric coordinates should be within 0.05 arcsec (optical) or 1 arcsec (radio) for a zenith distance of less than 70 degrees, better than 30 arcsec (optical or radio) at 85 degrees and better + /// than 20 arcmin (optical) or 30 arcmin (radio) at the horizon. + /// Without refraction, the complementary functions iauAtco13 and iauiauAtoc13 (P/Invoke internal) are self-consistent to better than 1 microarcsecond all over the celestial sphere. With refraction included, consistency falls off at high zenith distances, but is still better than 0.05 arcsec at 85 degrees.
+ /// It is advisable to take great care with units, as even unlikely values of the input parameters are accepted and processed in accordance with the models used.
+ ///
-
+ ///
"Observed" Az,ZD means the position that would be seen by a perfect geodetically aligned theodolite. (Zenith distance is used rather than altitude in order to reflect the fact that no + /// allowance is made for depression of the horizon.) This is related to the observed HA,Dec via the standard rotation, using the geodetic latitude (corrected for polar motion), while the + /// observed HA and RA are related simply through the Earth rotation angle and the site longitude. "Observed" RA,Dec or HA,Dec thus means the position that would be seen by a perfect equatorial with its polar axis aligned to the Earth's axis of rotation.
+ /// Only the first character of the type argument is significant. "R" or "r" indicates that ob1 and ob2 are the observed right ascension and declination; "H" or "h" indicates that they are hour angle (west +ve) and declination; anything else ("A" or + /// "a" is recommended) indicates that ob1 and ob2 are azimuth (north zero, east 90 deg) and zenith distance.
+ /// utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day. + /// However, JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the length is 86399, 86400 or 86401 SI seconds. + ///Applications should use the function iauDtf2d to convert from calendar date and time of day into 2-part quasi Julian Date, as it implements the leap-second-ambiguity convention just described.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// UT1-UTC is tabulated in IERS bulletins. It increases by exactly one second at the end of each positive UTC leap second, introduced in order to keep UT1-UTC within +/- 0.9s. n.b. This practice is under review, and in the future UT1-UTC may grow essentially without limit.
+ /// The geographical coordinates are with respect to the WGS84 reference ellipsoid. TAKE CARE WITH THE LONGITUDE SIGN: the longitude required by the present function is east-positive (i.e. right-handed), in accordance with geographical convention.
+ /// The polar motion xp,yp can be obtained from IERS bulletins. The values are the coordinates (in radians) of the Celestial Intermediate Pole with respect to the International Terrestrial Reference System (see IERS Conventions 2003), measured along the + /// meridians 0 and 90 deg west respectively. For many applications, xp and yp can be set to zero.
+ /// If hm, the height above the ellipsoid of the observing station in meters, is not known but phpa, the pressure in hPa (=mB), is available, an adequate estimate of hm can be obtained from the expression: + /// hm = -29.3 * tsl * log ( phpa / 1013.25 );
+ ///where tsl is the approximate sea-level air temperature in K (See Astrophysical Quantities, C.W.Allen, 3rd edition, section 52). Similarly, if the pressure phpa is not known, it can be estimated from the height of the observing station, hm, as follows: + ///phpa = 1013.25 * exp ( -hm / ( 29.3 * tsl ) );
+ ///Note, however, that the refraction is nearly proportional to the pressure and that an accurate phpa value is important for precise work.
+ /// The argument wl specifies the observing wavelength in micrometers. The transition from optical to radio is assumed to occur at 100 micrometers (about 3000 GHz).
+ /// The accuracy of the result is limited by the corrections for refraction, which use a simple A*tan(z) + B*tan^3(z) model. Providing the meteorological parameters are known accurately and + /// there are no gross local effects, the predicted astrometric coordinates should be within 0.05 arcsec (optical) or 1 arcsec (radio) for a zenith distance of less than 70 degrees, better than 30 arcsec (optical or radio) at 85 degrees and better + /// than 20 arcmin (optical) or 30 arcmin (radio) at the horizon. + /// Without refraction, the complementary functions iauAtco13 and iauAtoc13 are self-consistent to better than 1 microarcsecond all over the celestial sphere. With refraction included, consistency falls off at high zenith distances, but is still better than 0.05 arcsec at 85 degrees.
+ /// It is advisable to take great care with units, as even unlikely values of the input parameters are accepted and processed in accordance with the models used.
+ ///
-
+ ///
"Observed" Az,ZD means the position that would be seen by a perfect geodetically aligned theodolite. (Zenith distance is used rather than altitude in order to reflect the fact that no + /// allowance is made for depression of the horizon.) This is related to the observed HA,Dec via the standard rotation, using the geodetic latitude (corrected for polar motion), while the + /// observed HA and RA are related simply through the Earth rotation angle and the site longitude. "Observed" RA,Dec or HA,Dec thus means the position that would be seen by a perfect equatorial + /// with its polar axis aligned to the Earth's axis of rotation.
+ /// Only the first character of the type argument is significant. "R" or "r" indicates that ob1 and ob2 are the observed right ascension and declination; "H" or "h" indicates that they are + /// hour angle (west +ve) and declination; anything else ("A" or "a" is recommended) indicates that ob1 and ob2 are azimuth (north zero, east 90 deg) and zenith distance.
+ /// utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day. + /// However, JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the length is 86399, 86400 or 86401 SI seconds. + ///Applications should use the function iauDtf2d to convert from calendar date and time of day into 2-part quasi Julian Date, as it implements the leap-second-ambiguity convention just described.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// UT1-UTC is tabulated in IERS bulletins. It increases by exactly one second at the end of each positive UTC leap second, introduced in order to keep UT1-UTC within +/- 0.9s. n.b. This + /// practice is under review, and in the future UT1-UTC may grow essentially without limit.
+ /// The geographical coordinates are with respect to the WGS84 reference ellipsoid. TAKE CARE WITH THE LONGITUDE SIGN: the longitude required by the present function is east-positive + /// (i.e. right-handed), in accordance with geographical convention.
+ /// The polar motion xp,yp can be obtained from IERS bulletins. The values are the coordinates (in radians) of the Celestial Intermediate Pole with respect to the International Terrestrial + /// Reference System (see IERS Conventions 2003), measured along the meridians 0 and 90 deg west respectively. For many applications, xp and yp can be set to zero.
+ /// If hm, the height above the ellipsoid of the observing station in meters, is not known but phpa, the pressure in hPa (=mB), is available, an adequate estimate of hm can be obtained from the expression: + /// hm = -29.3 * tsl * log ( phpa / 1013.25 );
+ ///where tsl is the approximate sea-level air temperature in K (See Astrophysical Quantities, C.W.Allen, 3rd edition, section 52). Similarly, if the pressure phpa is not known, it can be estimated from the height of the observing station, hm, as follows: + ///phpa = 1013.25 * exp ( -hm / ( 29.3 * tsl ) );
+ ///Note, however, that the refraction is nearly proportional to the pressure and that an accurate phpa value is important for precise work.
+ /// The argument wl specifies the observing wavelength in micrometers. The transition from optical to radio is assumed to occur at 100 micrometers (about 3000 GHz).
+ /// The accuracy of the result is limited by the corrections for refraction, which use a simple A*tan(z) + B*tan^3(z) model. Providing the meteorological parameters are known accurately and + /// there are no gross local effects, the predicted astrometric coordinates should be within 0.05 arcsec (optical) or 1 arcsec (radio) for a zenith distance of less than 70 degrees, better + /// than 30 arcsec (optical or radio) at 85 degrees and better than 20 arcmin (optical) or 30 arcmin (radio) at the horizon. + /// Without refraction, the complementary functions iauAtio13 and iauiauAtoi13 (P/Invoke internal) are self-consistent to better than 1 microarcsecond all over the celestial sphere. With refraction included, + /// consistency falls off at high zenith distances, but is still better than 0.05 arcsec at 85 degrees.
+ /// It is advisable to take great care with units, as even unlikely values of the input parameters are accepted and processed in accordance with the models used.
+ ///
-
+ ///
"Observed" Az,ZD means the position that would be seen by a perfect geodetically aligned theodolite. (Zenith distance is used rather than altitude in order to reflect the fact that no + /// allowance is made for depression of the horizon.) This is related to the observed HA,Dec via the standard rotation, using the geodetic latitude (corrected for polar motion), while the + /// observed HA and RA are related simply through the Earth rotation angle and the site longitude. "Observed" RA,Dec or HA,Dec thus means the position that would be seen by a perfect equatorial + /// with its polar axis aligned to the Earth's axis of rotation.
+ /// Only the first character of the type argument is significant. "R" or "r" indicates that ob1 and ob2 are the observed right ascension and declination; "H" or "h" indicates that they are + /// hour angle (west +ve) and declination; anything else ("A" or "a" is recommended) indicates that ob1 and ob2 are azimuth (north zero, east 90 deg) and zenith distance.
+ /// utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day. + /// However, JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the length is 86399, 86400 or 86401 SI seconds. + ///Applications should use the function iauDtf2d to convert from calendar date and time of day into 2-part quasi Julian Date, as it implements the leap-second-ambiguity convention just described.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// UT1-UTC is tabulated in IERS bulletins. It increases by exactly one second at the end of each positive UTC leap second, introduced in order to keep UT1-UTC within +/- 0.9s. n.b. This + /// practice is under review, and in the future UT1-UTC may grow essentially without limit.
+ /// The geographical coordinates are with respect to the WGS84 reference ellipsoid. TAKE CARE WITH THE LONGITUDE SIGN: the longitude required by the present function is east-positive + /// (i.e. right-handed), in accordance with geographical convention.
+ /// The polar motion xp,yp can be obtained from IERS bulletins. The values are the coordinates (in radians) of the Celestial Intermediate Pole with respect to the International Terrestrial + /// Reference System (see IERS Conventions 2003), measured along the meridians 0 and 90 deg west respectively. For many applications, xp and yp can be set to zero.
+ /// If hm, the height above the ellipsoid of the observing station in meters, is not known but phpa, the pressure in hPa (=mB), is available, an adequate estimate of hm can be obtained from the expression: + /// hm = -29.3 * tsl * log ( phpa / 1013.25 );
+ ///where tsl is the approximate sea-level air temperature in K (See Astrophysical Quantities, C.W.Allen, 3rd edition, section 52). Similarly, if the pressure phpa is not known, it can be estimated from the height of the observing station, hm, as follows: + ///phpa = 1013.25 * exp ( -hm / ( 29.3 * tsl ) );
+ ///Note, however, that the refraction is nearly proportional to the pressure and that an accurate phpa value is important for precise work.
+ /// The argument wl specifies the observing wavelength in micrometers. The transition from optical to radio is assumed to occur at 100 micrometers (about 3000 GHz).
+ /// The accuracy of the result is limited by the corrections for refraction, which use a simple A*tan(z) + B*tan^3(z) model. Providing the meteorological parameters are known accurately and + /// there are no gross local effects, the predicted astrometric coordinates should be within 0.05 arcsec (optical) or 1 arcsec (radio) for a zenith distance of less than 70 degrees, better + /// than 30 arcsec (optical or radio) at 85 degrees and better than 20 arcmin (optical) or 30 arcmin (radio) at the horizon. + /// Without refraction, the complementary functions iauAtio13 and iauAtoi13 are self-consistent to better than 1 microarcsecond all over the celestial sphere. With refraction included, + /// consistency falls off at high zenith distances, but is still better than 0.05 arcsec at 85 degrees.
+ /// It is advisable to take great care with units, as even unlikely values of the input parameters are accepted and processed in accordance with the models used.
+ ///
-
+ ///
Scale identifies the time scale. Only the value "UTC" (in upper case) is significant, and enables handling of leap seconds (see Note 4).
+ /// For calendar conventions and limitations, see iauCal2jd.
+ /// The sum of the results, d1+d2, is Julian Date, where normally d1 is the Julian Day Number and d2 is the fraction of a day. In the case of UTC, where the use of JD is problematical, special conventions apply: see the next note.
+ /// JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The SOFA internal convention is that the quasi-JD day represents UTC days whether the length is 86399, + /// 86400 or 86401 SI seconds. In the 1960-1972 era there were smaller jumps (in either direction) each time the linear UTC(TAI) expression was changed, and these "mini-leaps" are also included in the SOFA convention.
+ /// The warning status "time is after end of day" usually means that the sec argument is greater than 60.0. However, in a day ending in a leap second the limit changes to 61.0 (or 59.0 in the case of a negative leap second).
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// Only in the case of continuous and regular time scales (TAI, TT, TCG, TCB and TDB) is the result d1+d2 a Julian Date, strictly speaking. In the other cases (UT1 and UTC) the result must be + /// used with circumspection; in particular the difference between two such results cannot be interpreted as a precise time interval.
+ ///
-
+ ///
Scale identifies the time scale. Only the value "UTC" (in upper case) is significant, and enables handling of leap seconds (see Note 4).
+ /// For calendar conventions and limitations, see iauCal2jd.
+ /// The sum of the results, d1+d2, is Julian Date, where normally d1 is the Julian Day Number and d2 is the fraction of a day. In the case of UTC, where the use of JD is problematical, special conventions apply: see the next note.
+ /// JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The SOFA internal convention is that the quasi-JD day represents UTC days whether the length is 86399, + /// 86400 or 86401 SI seconds. In the 1960-1972 era there were smaller jumps (in either direction) each time the linear UTC(TAI) expression was changed, and these "mini-leaps" are also included in the SOFA convention.
+ /// The warning status "time is after end of day" usually means that the sec argument is greater than 60.0. However, in a day ending in a leap second the limit changes to 61.0 (or 59.0 in the case of a negative leap second).
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// Only in the case of continuous and regular time scales (TAI, TT, TCG, TCB and TDB) is the result d1+d2 a Julian Date, strictly speaking. In the other cases (UT1 and UTC) the result must be + /// used with circumspection; in particular the difference between two such results cannot be interpreted as a precise time interval.
+ ///
-
+ ///
The TT date date1+date2 is a Julian Date, apportioned in any convenient way between the two arguments. For example, JD(TT)=2450123.7 could be expressed in any of these ways, among others: + /// + ///
+ ///+ /// + /// + /// + /// + ///+ /// Date 1 + ///+ /// Date 2 + ///+ /// Method + ///+ /// + ///+ /// 2450123.7 + ///+ /// 0.0 + ///+ /// JD method + ///+ /// + ///+ /// 2451545.0 + ///+ /// -1421.3 + ///+ /// J2000 method + ///+ /// + ///+ /// 2400000.5 + ///+ /// 50123.2 + ///+ /// MJD method + ///+ /// + ///+ /// 2450123.5 + ///+ /// 0.2 + ///+ /// Date and time method + ///The JD method is the most natural and convenient to use in cases where the loss of several decimal digits of resolution is acceptable. The J2000 method is best matched to the way the argument is handled internally + /// and will deliver the optimum resolution. The MJD method and the date and time methods are both good compromises between resolution and convenience. For most applications of this function the choice will not be at all critical. + ///
+ /// The equation of the origins is the distance between the true equinox and the celestial intermediate origin and, equivalently, the difference between Earth rotation angle and Greenwich + /// apparent sidereal time (ERA-GST). It comprises the precession (since J2000.0) in right ascension plus the equation of the equinoxes (including the small correction terms).
+ ///
-
+ ///
The TT date date1+date2 is a Julian Date, apportioned in any convenient way between the two arguments. For example, JD(TT)=2450123.7 could be expressed in any of these ways, among others: + /// + ///
+ ///+ /// + /// + /// + /// + ///+ /// Date 1 + ///+ /// Date 2 + ///+ /// Method + ///+ /// + ///+ /// 2450123.7 + ///+ /// 0.0 + ///+ /// JD method + ///+ /// + ///+ /// 2451545.0 + ///+ /// -1421.3 + ///+ /// J2000 method + ///+ /// + ///+ /// 2400000.5 + ///+ /// 50123.2 + ///+ /// MJD method + ///+ /// + ///+ /// 2450123.5 + ///+ /// 0.2 + ///+ /// Date and time method + ///The JD method is the most natural and convenient to use in cases where the loss of several decimal digits of resolution is acceptable. The J2000 method is best matched to the way the argument is handled internally + /// and will deliver the optimum resolution. The MJD method and the date and time methods are both good compromises between resolution and convenience. For most applications of this function the choice will not be at all critical. + ///
+ /// The equation of the origins is the distance between the true equinox and the celestial intermediate origin and, equivalently, the difference between Earth rotation angle and Greenwich + /// apparent sidereal time (ERA-GST). It comprises the precession (since J2000.0) in right ascension plus the equation of the equinoxes (including the small correction terms).
+ ///
-
+ ///
tai1+tai2 is Julian Date, apportioned in any convenient way between the two arguments, for example where tai1 is the Julian Day Number and tai2 is the fraction of a day. The returned + /// tt1,tt2 follow suit.
+ ///
-
+ ///
tai1+tai2 is Julian Date, apportioned in any convenient way between the two arguments, for example where tai1 is the Julian Day Number and tai2 is the fraction of a day. The returned + /// tt1,tt2 follow suit.
+ ///
-
+ ///
tai1+tai2 is Julian Date, apportioned in any convenient way between the two arguments, for example where tai1 is the Julian Day Number and tai2 is the fraction of a day. The returned utc1 + /// and utc2 form an analogous pair, except that a special convention is used, to deal with the problem of leap seconds - see the next note.
+ /// JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the + /// length is 86399, 86400 or 86401 SI seconds. In the 1960-1972 era there were smaller jumps (in either direction) each time the linear UTC(TAI) expression was changed, and these "mini-leaps are also included in the SOFA convention.
+ /// The function iauD2dtf can be used to transform the UTC quasi-JD into calendar date and clock time, including UTC leap second handling.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ ///
-
+ ///
tai1+tai2 is Julian Date, apportioned in any convenient way between the two arguments, for example where tai1 is the Julian Day Number and tai2 is the fraction of a day. The returned utc1 + /// and utc2 form an analogous pair, except that a special convention is used, to deal with the problem of leap seconds - see the next note.
+ /// JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the + /// length is 86399, 86400 or 86401 SI seconds. In the 1960-1972 era there were smaller jumps (in either direction) each time the linear UTC(TAI) expression was changed, and these "mini-leaps are also included in the SOFA convention.
+ /// The function iauD2dtf can be used to transform the UTC quasi-JD into calendar date and clock time, including UTC leap second handling.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ ///
-
+ ///
The result is computed even if any of the range checks fail.
+ /// Negative ihour, imin and/or sec produce a warning status, but the absolute value is used in the conversion.
+ /// If there are multiple errors, the status value reflects only the first, the smallest taking precedence.
+ ///
-
+ ///
The result is computed even if any of the range checks fail.
+ /// Negative ihour, imin and/or sec produce a warning status, but the absolute value is used in the conversion.
+ /// If there are multiple errors, the status value reflects only the first, the smallest taking precedence.
+ ///
-
+ ///
tt1+tt2 is Julian Date, apportioned in any convenient way between the two arguments, for example where tt1 is the Julian Day Number and tt2 is the fraction of a day. The returned tai1,tai2 follow suit.
+ ///
-
+ ///
tt1+tt2 is Julian Date, apportioned in any convenient way between the two arguments, for example where tt1 is the Julian Day Number and tt2 is the fraction of a day. The returned tai1,tai2 follow suit.
+ ///
-
+ ///
utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day.
+ /// JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the + /// length is 86399, 86400 or 86401 SI seconds. In the 1960-1972 era there were smaller jumps (in either direction) each time the linear UTC(TAI) expression was changed, and these "mini-leaps" are also included in the SOFA convention.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// The function iauDtf2d converts from calendar date and time of day into 2-part Julian Date, and in the case of UTC implements the leap-second-ambiguity convention described above.
+ /// The returned TAI1,TAI2 are such that their sum is the TAI Julian Date.
+ ///
-
+ ///
utc1+utc2 is quasi Julian Date (see Note 2), apportioned in any convenient way between the two arguments, for example where utc1 is the Julian Day Number and utc2 is the fraction of a day.
+ /// JD cannot unambiguously represent UTC during a leap second unless special measures are taken. The convention in the present function is that the JD day represents UTC days whether the + /// length is 86399, 86400 or 86401 SI seconds. In the 1960-1972 era there were smaller jumps (in either direction) each time the linear UTC(TAI) expression was changed, and these "mini-leaps" are also included in the SOFA convention.
+ /// The warning status "dubious year" flags UTCs that predate the introduction of the time scale or that are too far in the future to be trusted. See iauDat for further details.
+ /// The function iauDtf2d converts from calendar date and time of day into 2-part Julian Date, and in the case of UTC implements the leap-second-ambiguity convention described above.
+ /// The returned TAI1,TAI2 are such that their sum is the TAI Julian Date.
+ ///