/
x.jl
296 lines (217 loc) · 9.5 KB
/
x.jl
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
"""
xy06(date1, date2)
X,Y coordinates of celestial intermediate pole from series based
on IAU 2006 precession and IAU 2000A nutation.
### Given ###
- `date1`, `date2`: TT as a 2-part Julian Date (Note 1)
### Returned ###
- `x`, `y`: CIP X,Y coordinates (Note 2)
### Notes ###
1. 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:
| `date1` | `date2` | Method |
|:----------|:------------|:------------|
| 2450123.7 | 0.0 | JD |
| 2451545.0 | -1421.3 | J2000 |
| 2400000.5 | 50123.2 | MJD |
| 2450123.5 | 0.2 | date & time |
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 & time methods
are both good compromises between resolution and convenience.
2. The X,Y coordinates are those of the unit vector towards the
celestial intermediate pole. They represent the combined effects
of frame bias, precession and nutation.
3. The fundamental arguments used are as adopted in IERS Conventions
(2003) and are from Simon et al. (1994) and Souchay et al.
(1999).
4. This is an alternative to the angles-based method, via the ERFA
function [`fw2xy`](@ref) and as used in [`xys06a`](@ref) for example. The two
methods agree at the 1 microarcsecond level (at present), a
negligible amount compared with the intrinsic accuracy of the
models. However, it would be unwise to mix the two methods
(angles-based and series-based) in a single application.
### Called ###
- [`fal03`](@ref): mean anomaly of the Moon
- [`falp03`](@ref): mean anomaly of the Sun
- [`faf03`](@ref): mean argument of the latitude of the Moon
- [`fad03`](@ref): mean elongation of the Moon from the Sun
- [`faom03`](@ref): mean longitude of the Moon's ascending node
- [`fame03`](@ref): mean longitude of Mercury
- [`fave03`](@ref): mean longitude of Venus
- [`fae03`](@ref): mean longitude of Earth
- [`fama03`](@ref): mean longitude of Mars
- [`faju03`](@ref): mean longitude of Jupiter
- [`fasa03`](@ref): mean longitude of Saturn
- [`faur03`](@ref): mean longitude of Uranus
- [`fane03`](@ref): mean longitude of Neptune
- [`fapa03`](@ref): general accumulated precession in longitude
### References ###
- Capitaine, N., Wallace, P.T. & Chapront, J., 2003,
Astron.Astrophys., 412, 567
- Capitaine, N. & Wallace, P.T., 2006, Astron.Astrophys. 450, 855
- McCarthy, D. D., Petit, G. (eds.), 2004, IERS Conventions (2003),
IERS Technical Note No. 32, BKG
- Simon, J.L., Bretagnon, P., Chapront, J., Chapront-Touze, M.,
Francou, G. & Laskar, J., Astron.Astrophys., 1994, 282, 663
- Souchay, J., Loysel, B., Kinoshita, H., Folgueira, M., 1999,
Astron.Astrophys.Supp.Ser. 135, 111
- Wallace, P.T. & Capitaine, N., 2006, Astron.Astrophys. 459, 981
"""
function xy06(date1, date2)
x = Ref{Cdouble}()
y = Ref{Cdouble}()
ccall((:eraXy06, liberfa), Cvoid,
(Cdouble, Cdouble, Ref{Cdouble}, Ref{Cdouble}),
date1, date2, x, y)
return x[], y[]
end
"""
xys00a(date1, date2)
For a given TT date, compute the X,Y coordinates of the Celestial
Intermediate Pole and the CIO locator s, using the IAU 2000A
precession-nutation model.
### Given ###
- `date1`, `date2`: TT as a 2-part Julian Date (Note 1)
### Returned ###
- `x`, `y`: Celestial Intermediate Pole (Note 2)
- `s`: The CIO locator s (Note 2)
### Notes ###
1. 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:
| `date1` | `date2` | Method |
|:----------|:------------|:------------|
| 2450123.7 | 0.0 | JD |
| 2451545.0 | -1421.3 | J2000 |
| 2400000.5 | 50123.2 | MJD |
| 2450123.5 | 0.2 | date & time |
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 & time methods
are both good compromises between resolution and convenience.
2. The Celestial Intermediate Pole coordinates are the x,y
components of the unit vector in the Geocentric Celestial
Reference System.
3. The CIO locator s (in radians) positions the Celestial
Intermediate Origin on the equator of the CIP.
4. A faster, but slightly less accurate result (about 1 mas for
X,Y), can be obtained by using instead the [`xys00b`](@ref) function.
### Called ###
- [`pnm00a`](@ref): classical NPB matrix, IAU 2000A
- [`bpn2xy`](@ref): extract CIP X,Y coordinates from NPB matrix
- [`s00`](@ref): the CIO locator s, given X,Y, IAU 2000A
### Reference ###
- McCarthy, D. D., Petit, G. (eds.), IERS Conventions (2003),
IERS Technical Note No. 32, BKG (2004)
"""
xys00a
"""
xys00b(date1, date2)
For a given TT date, compute the X,Y coordinates of the Celestial
Intermediate Pole and the CIO locator s, using the IAU 2000B
precession-nutation model.
### Given ###
- `date1`, `date2`: TT as a 2-part Julian Date (Note 1)
### Returned ###
- `x`, `y`: Celestial Intermediate Pole (Note 2)
- `s`: The CIO locator s (Note 2)
### Notes ###
1. 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:
| `date1` | `date2` | Method |
|:----------|:------------|:------------|
| 2450123.7 | 0.0 | JD |
| 2451545.0 | -1421.3 | J2000 |
| 2400000.5 | 50123.2 | MJD |
| 2450123.5 | 0.2 | date & time |
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 & time methods
are both good compromises between resolution and convenience.
2. The Celestial Intermediate Pole coordinates are the x,y
components of the unit vector in the Geocentric Celestial
Reference System.
3. The CIO locator s (in radians) positions the Celestial
Intermediate Origin on the equator of the CIP.
4. The present function is faster, but slightly less accurate (about
1 mas in X,Y), than the [`xys00a`](@ref) function.
### Called ###
- [`pnm00b`](@ref): classical NPB matrix, IAU 2000B
- [`bpn2xy`](@ref): extract CIP X,Y coordinates from NPB matrix
- [`s00`](@ref): the CIO locator s, given X,Y, IAU 2000A
### Reference ###
- McCarthy, D. D., Petit, G. (eds.), IERS Conventions (2003),
IERS Technical Note No. 32, BKG (2004)
"""
xys00b
"""
xys06a(date1, date2)
For a given TT date, compute the X,Y coordinates of the Celestial
Intermediate Pole and the CIO locator s, using the IAU 2006
precession and IAU 2000A nutation models.
### Given ###
- `date1`, `date2`: TT as a 2-part Julian Date (Note 1)
### Returned ###
- `x`, `y`: Celestial Intermediate Pole (Note 2)
- `s`: The CIO locator s (Note 2)
### Notes ###
1. 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:
| `date1` | `date2` | Method |
|:----------|:------------|:------------|
| 2450123.7 | 0.0 | JD |
| 2451545.0 | -1421.3 | J2000 |
| 2400000.5 | 50123.2 | MJD |
| 2450123.5 | 0.2 | date & time |
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 & time methods
are both good compromises between resolution and convenience.
2. The Celestial Intermediate Pole coordinates are the x,y components
of the unit vector in the Geocentric Celestial Reference System.
3. The CIO locator s (in radians) positions the Celestial
Intermediate Origin on the equator of the CIP.
4. Series-based solutions for generating X and Y are also available:
see Capitaine & Wallace (2006) and [`xy06`](@ref).
### Called ###
- [`pnm06a`](@ref): classical NPB matrix, IAU 2006/2000A
- [`bpn2xy`](@ref): extract CIP X,Y coordinates from NPB matrix
- [`s06`](@ref): the CIO locator s, given X,Y, IAU 2006
### References ###
- Capitaine, N. & Wallace, P.T., 2006, Astron.Astrophys. 450, 855
- Wallace, P.T. & Capitaine, N., 2006, Astron.Astrophys. 459, 981
"""
xys06a
for name in ("xys00a",
"xys00b",
"xys06a")
f = Symbol(name)
fc = "era" * uppercasefirst(name)
@eval begin
function ($f)(date1, date2)
x = Ref{Cdouble}()
y = Ref{Cdouble}()
s = Ref{Cdouble}()
ccall(($fc, liberfa), Cvoid,
(Cdouble, Cdouble, Ref{Cdouble}, Ref{Cdouble}, Ref{Cdouble}),
date1, date2, x, y, s)
return x[], y[], s[]
end
end
end