-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathREADME.TXT
1708 lines (1291 loc) · 78.5 KB
/
README.TXT
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
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
ASTEROID LIGHTCURVE DATA BASE (LCDB)
Revised 2018 October 7
*******************************************************************************
SPECIAL NOTICES
*******************************************************************************
See Section 5 "SPARSE DATA AND WIDE-FIELD SURVEYS"
Mapping in LC_DAT file changed starting with HBAND column to allow
2-character field, e.g., SG instead of g, since upper/lower case
could be confusing.
The format of the LC_BINARY table changed signifiicantly for the Spring 2016
release. See Section 4.3 for more information.
Please review the column mappings for ALL tables. A number were modified for
the 2016 December release.
Starting with the 2017 annual release, a "basic" summary table is included
with the frequency-diameter plots based on that summary table. See Section
2.0.0 for important information on this file and its preferred use.
Releases on/after 2017 August 26 include a new file: LCDB_DAMIT.TXT. See the
discussion under 2.1.1.1 below.
Releases on/after 2017 November 10 include a new file: LCDB_DIAMETERS_PUB.TXT.
See the discussion under 2.1.0. Also, the LC_COLORINDEX_PUB.TXT file now
contains all entries, not just those that have a lightcurve period and/or
amplitude.
Updated Quality (U) Code definitions. See section 4.1.2.
*******************************************************************************
1.0.0 INTRODUCTION
--------------------------------------------------------------------------------
The Asteroid Lightcurve Data Base (LCDB) is a set of files generated from a
dBase IV data base that includes information directly and indirectly obtained
from observations made to determine the period and/or amplitude of asteroid
lightcurves. The information is taken from numerous journals and other sources.
It's main purpose is to provide a central location for basic information about
asteroid rotation rates and related information that can be used in statistical
studies involving a few or many parameters. Some of the data are obtained
directly from the observations while other data are inferred or calculated based
on orbital characteristics, assumed class, etc. Sections below explain in detail
which data are direct and indirectly obtained and, for the latter, their
derivation.
N.B. Even direct data should be confirmed by reference to the original works
whenever possible. Indirect data are provided for information purposes
only. They should NOT be used in critical studies.
1.1.0 AUTHOR INFORMATION
-------------------------
These data files are maintained by Brian D. Warner (Palmer Divide Observatory/
MoreData!, Alan Harris (MoreData!), and Petr Pravec (Astronomical Institute,
Czech Republic).
For basic information on the database or updated versions of the report files,
contact:
Brian D. Warner
Center for Solar System Studies / MoreData!
446 Sycamore Ave.
Eaton, CO 80615
brian@MinorPlanetObserver.com
For more theoretical details and discussions, contact
Alan Harris
MoreData!
4603 Orange Knoll Ave.
La Canada, CA 91011 USA
harrisaw@att.net
1.2.0 DISCLAIMER
-----------------
We have made every attempt to keep the data up to date and correct. However, we
know that there is the possibility for omissions or errors. Please let us know
of any corrections or additions by sending email to one of the below.
Brian D. Warner brian@MinorPlanetObserver.com
Alan Harris harrisaw@att.net
2.0.0 DATA FILES
--------------------------------------------------------------------------------
The data files in this release consist of two primary sets. The general files
and the Binary Asteroid files provided by Petr Pravec, Astronomical Institute,
Czech Republic.
The general text files contain the most critical information from all the main
data tables (lookup tables are not included).
The main exception is the F-D_<Release Date>_PUB_BASIC.TXT file. This contains
the data used to generate the frequency-diameter plots included in the release.
THIS FILE DOES NOT INCLUDE U <= 1+, WIDE-FIELD, OR SPARSE-DATA OBJECTS.
We chose to limit this file to preclude data that we consider less than
fully-reliable for rotation or other studies.
We STRONGLY urge that the F-D*_PUB_BASIC.TXT file be used as the base for
initial studies and/or used as a background upon which to plot new results
to show that they either fit the background, or reveal something profoundly
new.
Should there be a need for the excluded data, they can be extracted from the
LC*.TXT files using the column maps and descriptions for each table.
2.0.1 AVAILABILITY OF RAW DATA FILES
-------------------------------------
The raw databases files are not available since they are in a proprietary
format. We can, on a limited basis, provide CSV files generated from the
database files. Contact the authors detailing the reaons for needing the
files and if there are any special requirements to be considered.
2.1.0 GENERAL FILES
--------------------
README.TXT This file of introductory information.
LC_DAT_PUB.TXT The lightcurve data file, with data from individual
references
LC_SUM_PUB.TXT Summary data, one line per asteroid, no references.
LC_REF.TXT Reference list to all published lightcurve data.
LC_AMBIGUOUS_PUB.TXT Separate summary/detail file for asteroids with ambiguous
periods
LC_BINARY_PUB.TXT Separate summary/detail file for binary asteroids
LC_NPA_PUB.TXT Separate summary/detail file for "tumbling" asteroids
LC_SPINAXIS_PUB.TXT Separate summary/detail file for asteroids with spin axis
results
LC_NOTESEX_PUB.TXT Additional notes for Summary/Details entries
LC_COLORINDEX_PUB.TXT Separate summary/detail file for color indices of
asteroids
LC_DIAMETERS_PUB.TXT Separete summary/detail file for diameters found by
thermal, occultation, radar, or other observations.
2.1.1 SPIN AXIS CATALOGS
-------------------------
As noted above, the LC_SPINAXIS_PUB.TXT file stores information about the spin
axis properties (ecliptic coordinates and sidereal periods). A more complete and
thorough catalog is maintained by Kryszczynska et al. at the Poznan Observatory
in Poland.
That catalog can be accessed via
http://vesta.astro.amu.edu.pl/Science/Asteroids/
Josef Durech also maintains a list of spin axis solutions, with shape models and
data files. His site is at
http://astro.troja.mff.cuni.cz/projects/asteroids3D/
It should be noted that the favored DAMIT pole may differ from the one in the
original reference. This is likely because the original data were used by Durech
and associates in a new analysis. Their revised result replaced the original
instead of indicating a new result under a different reference.
Because of the complexities of cross-checking the LCDB vs. DAMIT vs. the original
result, the LCDB does not directly include any DAMIT results, i.e., there are
no entries with DAMIT being the author reference. When and if revised results are
published in one of the journals, those results will included in the LCDB.
2.1.1.1 DAMIT CATALOG (LCDB_DAMIT.TXT)
---------------------------------------
The public release of the LCDB text files now includes a file that summarizes
the DAMIT catalog by merging the data and reference files from the site. The
LCDB_DAMIT file is updated with the latest entries from the DAMIT site for
each public release. In addition, the summarized data are included in MySQL
tables used on the ALCDEF (alcdef.org) and MinorPlanet.info web sites and
included in some of the reports generated on those sites.
Field Header Format Pos Notes
--------------------------------------------------------------------------------
Number NUMBER I7 1-7 Blank if no MPC assigned number
Name NAME A20 9-28 Name or designation
Citation CITATION A20 30-64 Short reference, e.g., Torppa et al. (2003)
L1 L1 I3 66-68 Ecliptice longitude (J2000) of pole
B1 B1 I3 71-73 Ecliptice latitude (J2000) of pole
Period PERIOD F12.8 77-88 Sidereal period, hours
Quality QF A5 91-95 Quality rating of pole (see DAMIT docs)
Reference REFERENCE A43 97-139 Detailed reference (see NOTES)
Page PAGE A10 141-150 Page number(s) in reference (see NOTES)
Notes:
--------------
The DAMIT catalog has two reference ID columns. The primary is RefID; the other is
RefIDObsolete, which is mainly for an entry that has since be supplanted by a newer
model. If a Citation entry is followed by '*', this means that there were multiple
references in the RefID column, with the first entry used for the line in the text.
If the Citation entry is followed by '#', this means that the line is based on the
first of two or more refernces in the RefIDObsolete column. There is no marker to
indicate if a single reference for the line used the RefID or RefIDObsolute column.
There is some inconsistency in the DAMIT entries regarding the full reference. In
particular, whether or not the page number was part of the value in the Publication
column. For these reason, the values in the Publication and Page columns were taken
at face value, with the exception that journal names were made consistent.
For example, there were several variations on "Astronomy & Astrophysics." These
were all changed to "Astron. Astrophys."
2.2.0 BINARY ASTEROID FILES
----------------------------
The following files are maintained by Petr Pravec. These files are considerably
more detailed than what's in LC_BINARY_PUB and so are better suited for critical
studies.
BINARY_README.TXT Separate README pertaining the binary asteroid
BINASTD_PUB.TXT The best estimates of compiled parameters
BINASTE_PUB.TXT Uncertainties of the estimates in BINASTD_PUB.TXT
BINASTM_PUB.TXT References and notes for the compiled estimates
BINASTR_PUB.TXT Information on each of the estimates, e.g., their derivation
These files are available at
http://www.asu.cas.cz/~asteroid/binastdata.htm
2.2.1 ABOUT BINARY DATA
------------------------
The data in the LC_BINARY_PUB.TXT file are by no means exhaustive. They are
meant to provide a quick overview of the parameters for a binary (or multiple)
system.
The reader is urged to consult the original journal articles for more complete
details.
A good summary page with links to those journal references is the web site run
by by Wm. Robert Johnston
http://www.johnstonsarchive.net/astro/asteroidmoons.html
Another summary database, the Virtual Observatory Binary Asteroids Database (VOBAD),
is maintained at UC Berkeley/SETI Institute by Franck Marchis, Brent Macomber, et al.
http://cilaos.berkeley.edu/PHP_scripts/VOBAD/VOBAD_portal.html
3.0.0 LCDB DATA
--------------------------------------------------------------------------------
The original lightcurve database was a simple text file with a structure that
tried to minimize disk space requirements. That served well for many years.
However, the rapidly growing number of lightcurves being reported as well as the
file's format not being able to accommodate some data prompted a change starting
in mid-2006.
The foremost change was converting to a relational database that includes
numerous tables and has SQL search capabilities. This allows for not only easier
maintenance of the database but for generating reports in a new way that are
more informative, complete, and constant in formatting.
The format of the report files has changed from previous years. Some significant
changes were made for the Spring 2016 release to include additional output fields.
Third-party parsing programs will need to be modified to handle the changes. See
the revised column mappings in Section 4.
The sections below provide the formatting for each field and the reports. This
should make rewriting old parsing programs, or new ones, fairly straightforward.
3.1.0 DIRECT DATA
------------------
Data that is obtained directly from photometric observations includes
1. Rotation period (usually synodic).
2. Amplitude.
3. Absolute magnitude, H, and phase slope parameter, G, when determined by
using reduced magnitude versus phase angle data.
4. Binarity due to mutual events, i.e., occultations and eclipses. In such
cases, the rotation period of the primary and orbital period of the
satellite and the amplitude of the primary lightcurve are the usual direct
results. The size ratio can be computed from the depth of the events.
For more details on binary lightcurve analysis, see Pravec et al., 2006,
Icarus 181, 63-93.
5. Color indices.
6. Diameter if based on stellar occultation or adaptive optics/radar. Radar
diameters can also be considered indirect, depending on how the diameter
was determined.
7. Taxonomic class.
3.1.1 SYNODIC VERSUS SIDEREAL PERIOD
-------------------------------------
The synodic period depends on viewing aspect and the rate of motion of the
asteroid across the sky. An expression for the magnitude of the expected
difference between the sidereal period and synodic period based on the Phase
Angle Bisector (PAB) is
DeltaP = [d(PAB)/dt] * P^2
Where DeltaP difference between synodic and sidereal periods, in units
of the rotation period (usually hours).
[d(PAB)/dt] angular rate of change in the Phase Angle Bisector in
inverse units of the rotation period, e.g., in units
of cycles/hour
P the rotation period of the asteroid in the same units of
time, e.g., hours/cycle
For example, assume an asteroid with a rotation period of 8 hours observed when
the PAB is changing by 0.05 deg/day (typical for an main-belt asteroid at
opposition), then the sidereal-synodic difference is
DeltaP = [0.05 / 360.0 / 24.0] * (8 ^ 2) = 0.00037 hr.
cycles / hour hours^2/cycles^2 hours / cycle
The synodic-sidereal difference can be either positive or negative, and can
exceed the value given by this expression for near-polar aspects, but the
expression gives a reasonable estimate of the magnitude of the expected
difference.
In most cases, the period given in the summary and details lines are synodic and
not sidereal. An 'S' flag (see notes below) indicates that the period is
sidereal. There are many entries in both tables that do not carry the 'S' flag
when they should. This is part of the legacy nature of the data after converting
the files to the new data base, i.e., the old format did not allow for
indicating the period was one type or another. We hope to update these and other
legacy values that now have qualifying flags in future versions.
For most studies, the difference between sidereal and synodic period is not
significant.
3.1.2 INDIRECT DATA
--------------------
Indirect data is that obtained by calculation and/or assumption.
N.B. THESE DATA ARE PROVIDED FOR CONVENIENCE ONLY, AND SHOULD NOT BE USED FOR
STATISTICAL STUDIES, NOR ASSUMED TO BE ACCURATE AND CURRENT.
1. Diameter, H, and albedo (Pv, Pr, etc.).
The relationship between H, diameter, and albedo is:
D = (1329km) * 10.0^(-0.2*H) / sqrt(albedo)
or
logD (km) = 3.1235 - 0.2H - (0.5 * log(albedo)).
(See Pravec and Harris, 2007. Icarus 190, 250-259).
The value of H is usually known, though not always accurately, based on
photometric observations. If direct data are available for D and/or Pv,
then the above relationships can be used to derive a missing quantity.
Data from the SIMPS study (Tedesco, E.F., Noah, P.V., Price, S.D.: 2004,
IRAS Minor Planet Survey. IRAS-A-FPA-3-RDR-IMPS-V6.0. NASA Planetary Data
System) is used when available and no overriding data are available. If a
newer value of H than that used by SIMPS is available, the diameter and
albedo are re-computed based on Harris and Harris (1997, Icarus 126,
450-454).
If the diameter was based on an assumed albedo and H is revised, the albedo
is held constant and the diameter re-computed using the above formulae.
If the diameter was determined by radar, resolved imagery, etc. and a new
H is available, the diameter is held constant and the albedo is
re-computed.
2. Taxonomic Class, orbital class, and albedo
These three values can have a complex relationship when the class and
albedo are not directly obtained.
When spectroscopic or other data are available that can determine the
taxonomic class exactly but no direct albedo data are available, the albedo
can be assumed. This albedo can, in turn, be used to find the estimated
diameter and/or H if those quantities are not directly known.
Flags in the Summary table indicate the source of these fields, including
if they are assumed based on a combination of available data. The table
below shows the assumed values used barring any direct data.
The family/group is based on orbital parameters. These are mostly for
informational purposes only since the definition for some groups or
families is "fuzzy", at best. Note the distinction between a family and
group. A family is a set of asteroids with a common parent body. A group
is a set of asteroids with common orbital characteristics. Members of a
family will almost always be in the same group, but members of a group may
not necessarily be of the same family.
For a more complete discussion of this topic, see Warner et al. (2009)
Icarus 202, 134-146. This paper includes new default albedo and G values
for given taxonomic classes based on the data in the LCDB.
Group/Family Source/orbital parameters Class Pv Note
-------------------------------------------------------------------------------------------
Baptistina Bottke el al C 0.057
Centaur 5.5 < a <= 30 C 0.057
Centaur Comet Centaur w/comet behvaior C 0.057 9
Comet-like orbit Q > 5.0 C 0.057 4
Comet exhibits coma and/or tail C 0.057
Eos 2.99 < a < 3.03, 0.01 < e < 0.13, 8 < i < 12 S 0.14
Erigone 2.32 < a < 2.40, 0.15 < e < 0.22, 4 < i < 6 C 0.057
Eunomia 2.53 < a < 2.72, 0.08 < e < 0.22, 11 < i < 16 S 0.21
Flora 2.15 < a < 2.35, 0.03 < e < 0.23, 1.5 < i < 8 S 0.24
Hilda 3.7 < a < 4.2, 0.07 < e, i < 20 C 0.057
Hungaria 1.78 < a < 2.0, e < 0.18, 16 < i < 34 ES 0.3 1
Karin Nesvorny, private communications S 0.26
Koronis 2.83 < 2.91, e < 0.11, i <= 3.5 S 0.24
Main belt - inner a < 2.6 S 0.20 5
Main belt - inner comet a < 2.6 C 0.057 9
Main belt - middle 2.6 < a < 2.7 SC 0.10
Main belt - middle comet 2.6 < a < 2.7 SC 0.10 9
Main belt - outer 2.7 < a < 5.0 C 0.057
Main belt - outer comet 2.7 < a < 5.0 C 0.057 9
Mars crosser 1.3 < q < 1.668, Q < 5.0 S 0.20 5
NEA (Apollo/Aten/Amor) q < 1.3 S 0.20 5
NEA (comet) q < 1.3 C 0.057 9
Nysa 2.4 < a < 2.5, 0.12 < e < 0.21, 1.3 < i < 4.3 S 0.20 6
Phocaea 2.25 < a < 2.5, e >= 0.1, 18 < i < 32 S 0.23
Planet Satellite 7
Themis 3.08 < a < 3.24, 0.09 < e < 0.25, i <= 3 C/B 0.08
TNO/KBO a > 30 C 0.1
Trojan - Jupiter 5.05 < a < 5.4 C 0.057
Trojan - Mars similar to Mars S 0.20 5
Trojan - Neptune similar to Neptune C 0.057
Trojan - Saturn similar to Saturn C 0.057 2
Trojan - Uranus similar to Uranus C 0.057 2
Vestoid 2.26 < a < 2.48, 0.03 < e < 0.16, 5 < i < 8.3 S 0.20 3
NOTES
-----
1 Pv = 0.3 is a compromise value when no taxonomic information is
available, since the Hungarias are both a family (common parent, E/X
class, pv = 0.4) and group (similar orbits, S class, Pv = 0.20).
2 None known and not likely due to perturbations by giant planets, both
interior and exterior.
3 Higher albedo (0.4) assigned only if in V class determined (SMASS, etc).
Otherwise, class is 'S' and Pv = 0.20 on presumption that the object
shares orbital characteristics but not parent body.
4 Barring any other classification that meets Q > 5, the orbit is
classified as "comet-like."
5 The default Pv = 0.20 ± 0.07 for S-type objects was derived from the
geometric mean of all S-type objects in the LCDB with known albedos
(usually SIMPS).
6 The Nysa orbital space is polluted by a large portion of objects that
are not true members of the Nsya-Hertha family and even then, the true
members are heterogeneous in nature. For this reason, we elected to
treat the Nysa space the same as other unassociated inner main belt
objects by using a default of S class and Pv = 0.20.
7 The Planet satellite group includes small and distant natural satellites of the major
planets, e.g., Himalia Jupiter VI. They are included since a number of
these smaller bodies resemble asteroids in size and rotational properties.
9 Several orbital groups have been given a "comet" subclass. This is for
objects within the given orbital class that have shown cometary activity,
e.g., so-called "main belt comets." The Comet class is reserved for "true"
comets, e.g., P/Encke and the Comet-like orbit class is still reserved for
objects that have very elongated orbits but have shown no signs of cometary
activity. These "comet" subclasses are given default taxonomic class of 'C'
and albedo of 0.057.
Bottke, W.F., Vokrouhlicky, D., Nesvorny, D. (2007). Nature 449, 48-53, and
private communications.
3. Color Index applied to H
Color index is not generally assumed or entered into the LCDB. However,
some times the value of H was found in a photometric band other than V,
e.g., Cousins R. In that case, and if the value is used to override the H
given by SIMPS or the MPCORB file (Minor Planet Center) in the Summary
line, H is transformed to the V band. When the color index is not directly
available, these values are used to transform the measured H value
V-R 0.45
B-V 0.80
V-r' 0.23
When such a transform is used in the Summary line, whether or not based on
an assumed value, the H value has the 'T' (transformed) flag.
4.0.0 LCDB FILE DESCRIPTIONS
--------------------------------------------------------------------------------
The following sections describe the specific files that are part of the LCDB
release, not including the Binary files from Petr Pravec. A column map is
provided for each report that is part of the release. In addition, sub-sections
describe the meaning of the flags that qualify various fields in the report.
4.0.1. FILE STANDARDS
----------------------
All files are simple ASCII text with Windows (PC) line terminators (CRLF).
Unless stated otherwise, all files are single-space delimited, i.e., there is a
one-character blank column between the end of one field and the start of the
next.
4.1.0 LC_SUM_PUB AND LC_DAT_PUB
--------------------------------
These are the primary files in the LCDB release. Both have the same column
mapping. They show both direct and indirect data, the most important being the
direct data of lightcurve period and amplitude along with our assessment of the
quality of the period solution. The latter is expressed by the U code, which is
described in detail below.
In the LC_DAT_PUB file, a Summary line is followed by one or more Details lines.
The Summary line is our best determination of the primary information for a
given object based on the data in the Details lines. For example, where several
periods are available, the Summary line uses the one that we consider the most
likely to be correct. Sometimes that value may be an average of the available
values.
The Details lines differ in formatting only in that the number and name of the
asteroid are replaced by a "short reference" name that will be found in the
LC_REF_PUB references file.
4.1.1 MULTIPLE DETAILS TABLE ENTRIES
-------------------------------------
In some cases, there is more than one detail line under a given asteroid with
the same publication reference. This is deliberate in order to allow statistical
studies of lightcurve amplitude versus phase versus class (albedo).
For example, if a single publication reports the lightcurve behavior for an
asteroid where the synodic period and/or amplitude of the curve changed
significantly during the course of the observations, the Details table includes
an appropriate number of entries. Those entries will "split out" the results so
that the period and/or amplitude can be tied to a specific (though maybe only
approximate) set of PAB or Phase values. A good example would be a paper
reporting observations of an NEA asteroid over several weeks where the amplitude
of the curve went from 1.1 to 0.3 magnitudes over the range of observations.
In most cases, splitting the results into distinct sets was not difficult, e.g.,
the asteroid was observed on one night at one-week intervals. In some cases, the
split was not so distinct. In this case, compromises were made in order to avoid
having an excess of multiple entries while still retaining sufficient resolution
of the variations versus time.
A variation on the above is if the author(s) forced the data from several blocks
of dates to fit a fixed period solution. Here, the period will be the same for
all entries, though the amplitude may change. In this case, the period is left
blank. The U code is assigned for each lightcurve based on the presumption that
the fixed period is correct, i.e., it is based on the quality of the fit of the
data to the presumed period. The main point of interest is the amplitude for the
reasons given above. Other information that was derived based on the given block
of data, e.g., a value for H, G, or a color index, will be included within that
Details record as well so that it's clear which block of data was used to derive
the given values.
4.1.2 U (QUALITY) CODE
-----------------------
The U code provides our assessment of the quality of the period solution, not
necessarily of the data per se. The uniqueness of the solution, while an
important factor, is not the sole consideration in making an assessment.
Depending on the specifics for a given asteroid, a good period solution can be
obtained by using a large amount of lesser quality data about as well as using
less data that is of higher quality. Many factors come into play making the
assessment. The table below gives the general outline of the criteria used,
going from highest to lowest rating.
3 The lightcurve is completely unambiguous in terms of period, i.e.,
there are no cycle ambiguities or possible solutions with single,
triple, or other number of extrema. The coverage of the entire rotation
phase is to the degree than any remaining small gaps can be confidently
interpolated.
3- A unique period determination, but possibly some moderate gaps in
coverage, enough so that interpolation of the entire curve is not
certain, but not enough to allow any other solution. Also, while
the period is "unique", it may still be wrong by a small amount due
to outliers, large scatter in relation to the lightcurve amplitude,
lightcurve evolution over the range of observations or tumbling that
leads to imperfect overlapping at some parts of the lightcurve,
and/or not finding the period to a high enough precision.
2+ It is unlikely but not impossible that the period is in error due to
cycle counts or alternate numbers of extrema per cycle, and no more
than moderate gaps in coverage (as in U = 3-).
2 Result based on less than full coverage, so that the period may be wrong
by 30 percent or so. Also, a quality of 2 is used to note results where
an ambiguity exists as to the number of extrema per cycle or the number
of elapsed cycles between lightcurves. Hence the result may be wrong by
an integer ratio.
2- Period and total amplitude not firmly established. For example, a single
night coverage of about half a cycle including a maximum and minimum,
but not enough to actually derive an accurate period. This is the
minimum reliability code that we accept for statistical analysis.
1+ Similar to U = 2-, but with less amplitude so that it is not absolutely
certain that the variations are true rotational variation and not due to
noise, etc.
1 May be completely wrong. What is interpreted as rotational variation
may be just noise, calibration error, etc.
1- Probably wrong. A lightcurve that may be completely wrong (as in U = 1)
but, in addition, the claimed period is very unlikely, e.g., a large
object with a claim of P < 2h.
0 Result later proven incorrect. This appears only on records of
individual observations.
It is important to keep in mind that U = 0 does not necessarily mean
that the data for a given lightcurve are of low quality. The only
interpretation that should be inferred is that the -reported solution-
has been determined, perhaps from subsequent data, to be incorrect so
that not even the loose constraints of U = 1 or U = 2 can be used. For
the most part, U = 0 will be used very sparingly and the previous U
rating (unless 3) will be retained to avoid the false impression that
the data are of limited or no use.
N.B. Until the intermediate release in 2008 November, the LCDB also used a
value of '4' for the U code, which indicated that a pole solution had
been reported. This is no longer the case since, in the past, there have
been cases where a 4 was assigned because there was a pole solution given
but the best available period solution was no better than 2.
The period solution quality is now indepedent of any pole solution. A
separate "Pole" flag in the Summary and Details reports is used to
indicate that a pole solution has been reported. The LC_SPINAXIS_PUB file
includes more details and its own quality code assignment.
Assignment of the refined ratings using a + or - is a work in progress as we
catch up with almost 20 years of data entry. Therefore, not all U code ratings
will match what we would give under current rules and are subject to change.
If a summary line contains U = 3 it should be understood that, by implication,
any detail lines with U < 3 are superceded in terms of period determination.
We will generally retain the U rating assigned to a prior U < 3 result if the
period derived lies close within its undertainty range to the later adopted
U = 3 period, as an indicator of the quality of the observations reported.
In the case where U < 3 in the summary line, then one or more detail lines may
be assigned U = 0, but only if it is firmly established that, while we
cannot say for certain what is the correct period, we can say with certainty
that the period claimed in the reference is wrong (i.e., discordant with
subsequent data).
Some Details lines, and even some Summary, may not contain a U code rating. This
is deliberate and can be for several reasons.
1. The available data do not include a lightcurve, therefore, it is not
possible to give a rating to the curve. In some cases, where the results
are reported by observers whose standard of work is known to be of
sufficient quality, we may assign an interim U code, usually 2, until a
lightcurve or the data are available.
2. In the case where several results are published for a given object in the
same reference, we will assign a U code rating for the "best" available
data and include only new information for that given Details record, e.g.,
see section 4.1.1, "Multiple Details Table Entries."
There are instances when data are available they do not reasonably define a
period or even constrain a range in which the period lies. In addition, the data
may not be able to provide any reasonable indication of the amplitude. In these
cases, the entry in the Details record will have the reference to the work and
blank U code rating and no period or amplitude.
The Summary line may also have no period and/or amplitude as well as U = <blank>.
This occurs when none of the Detail lines, even if they have some or all of the
information, is deemed insufficiently reliable so as to put the information in the
Summary line. This is done to show that there are data available for the object
but that they may be of very limited use.
4.1.3 LC_SUM_PUB AND LC_DAT_PUB COLUMN MAPS
--------------------------------------------
In the LC_DAT_PUB file, there is a blank line between the last detail line for a
given object and the Summary line for the following object.
Field Header Format Pos Notes
--------------------------------------------------------------------------------
Number NUMBER I7 1-7 Blank if no MPC assigned number
EntryFlag (EF?) A1 9 * new record since last pubic release (see notes)
Name NAME A30 11-40 Summary: Name or designation
Details: Publication reference
Desig DESIG A20 42-61 Summary: MPC Designation (see notes)
Details: Appxoimate mid-date of observations
Family FAM A8 63-70 Family/Group association
CSource (CS?) A1 72 Source of taxonomic class
Class CLASS A5 74-78 Taxonomic class
DSource (DS?) A1 80 Source of diameter
DFlag (DF?) A1 82 Diameter flag
Diameter DIA. F9.4 84-92 in km
HSource (HS?) A1 94 Source of H value
H H F5.2 96-100 H (absolute magnitude)
HBand (HB?) A2 102 BVRI,S(UGRIZ), V if Blank
ASource (AS?) A1 105 Source of albedo value
AlbedoFlag (AlF?) A1 107 Albedo qualifier (> or <)
Albedo A F6.4 109-114 Albedo
PFlag (PF?) A1 116 Period qualifier
Period PERIOD F13.8 118-130 Period, in hours
PDescrip P DESC A15 132-146 Period description if not numeric value,
e.g., long
AmpFlag (AmF?) A1 148 Amplitude flag
AmpMin AMIN F4.2 150-153 Minimum amplitude of a range. (See Notes)
AmpMax AMAX F4.2 155-158 Maximum amplitude of a range OR (See Notes)
amplitude if no range.
U U A2 160-161 Lightcurve Quality
Notes NOTES A5 163-167 Qualifying flags for lightcurve record
Binary BIN A3 169-171 Binary Flag
Private PRI A3 173-175 Y = Unpublished, contact named observer
to request details
Pole SAM A3 177-179 Spin Axis and/or Shape Model available
SparseData SD A2 181-182 Y = Result based on sparse data (see Sec. 5)
WideField WF A2 184-185 Y = Result based on wide field data (see Sec. 5)
Notes:
--------------
Entry flags (column 9)
The once-a-year "official" release of the LCDB will have only of two values in
column 9
<blank> The entry was last entered/updated more than one annual release
prior to the current version.
* The entry is new since the last annual release.
O (Capital O) The summary record is an "orphan", i.e., no lightcurve data
have been reported. However, other data such as color indices, H-G values,
etc. may have been reported and so a record is created in the summary
table with the hope that lightcurve data will be reported.
The only time orphaned summary records are included is in the color index
and diameters tables. Otherwise, fewer than 30% of the entries in the
color index table and an even smaller percentage of the diameter table
entries would be available in the public release.
Intermediate releases, those not fully vetted and so offered "as-is", might
contain other values in column 9, e.g., '@' and '!'. These are "bookkeeping"
marks used during the vetting process. The only thing to be inferred from them
is that the entry has yet to be validated, is subject to change, and may
eventually appear with the '*' flag.
Summary records marked private include only the U code and private flag. The
accompanying Details line(s) include only the author, and the U code. This
allows the LCDB user to know that there is a lightcurve available and its
source. He should contact the author to inquire about the results and
availability of data.
The DESIG field in the Summary line is reserved for the official MPC designation
only. It is not used to record survey/catalog specific IDs. It can be the same
as in the NAME field until the object is given an official name by the IAU.
Asteroids 1 - 332 do not have MPC designations.
The DESIG field in the Detail line gives the mid-date of observations, if available,
in yyyy-mm-dd format, e.g., February 20, 2001 = 2001-02-20. It is this date for
which the phase angle and phase angle bisector values are computed.
For example,
70030 * Margaretmiller 1999 CZ1
Warner 2005f 2003-10-06
Warner 2010k 2003-10-06
Warner 2010k 2010-02-15
As opportunities allow, the Details DATEOBS field will be updated to give the
mid-date of observations for a specific data set.
The Min/Max Amplitude values in the Summary table are based only on detail
lines that have a U >= 2- ratings. If the U code is empty or U <= 1+, the
detail line min/max amplitudes are not considered.
4.1.4 FIELD (FLAG) CODES USED IN SUMMARY AND DETAIL LINES
----------------------------------------------------------
The flags appear in the data field immediately before the value they qualify. In
most cases, they are a single character.
ALBEDOFLAG (Albedo Qualifier)
-----------------------------
Blank NONE
< Less than
> Greater than
AMPFLAG (Amplitude Flag)
------------------------
Blank NONE
< Less than
> Greater than
ASOURCE (Albedo, SUMMARY)
-------------------------
Blank Default = measured
A Assumed (based on class - known or assumed)
C Caculated from H and Diameter
D Derived (usually from IR measurements were diameter is measured directly)
M Measured (radiometric or polarimetric observations)
ASOURCE (Albedo, DETAILS)
-------------------------
Blank Unknown source
A Assumed (based on class - known or assumed)
D Derived (based on H and/or D being known; Harris & Harris method)
L Taken from Details List entry
S SIMPS (IRAS Minor Planet Survey)
BIN (Binary Flag)
-----------------
Blank NONE
? Possible, usually due to lacking mutual eclipse/occultation events
B Binary system
M Multiple system, more than two
If the '?' flag appears in a detail line, the author made a claim that the
object is or may be a binary. If the '?' also appears in the summary line,
we regard the claim as credible.
If '?' appears only in the detail line and not in the summary line, we regard
the binary claim as spurious or unfounded.
CSOURCE (Class Source)
----------------------
Blank NONE
A Assumed (see discussion 3.1.2, "Indirect Data");
B SDSS-Bus (derived by Bus et al. from SDSS colors)
L Details List
M SDSS-MFB (derived by Masi et al. from SDSS colors)
S SMASS I/II
T Tholen et al, Asteroids II
DFLAG (Diameter Flag)
---------------------
Blank NONE
< Less than
> Greater than
DSOURCE (Diameter Source)
-------------------------
Blank NONE
C Calculated A/H Based on assumed albedo and MPCORB H - see discussion
below
D Derived A/H Recalculated from determined albedo and/or H - see
discussion below
L Details List Taken directly from a details list value
S SIMPS Supplementatl IRAS Minor Planet Survey
EntryFlag
---------
Blank Pre-existing record.
* New or updated record since the last release.
FAMILY (ORBITAL GROUP)
----------------------------------
Blank No group or family determined
BAP Baptistina
CEN Centaur
CEN-C Centaur - comet behavior (coma and/or tail)
CLO Comet-like orbit
CMT Comet
EOS Eos
ERI Erigone
EUN Eunomia
FLOR Flora
H Hungaria
HIL Hilda
KAR Karin
KOR Koronis
MB-I Main belt - inner
MB-IC Main belt - inner, comet behavior (coma and/or tail)
MB-M Main belt - middle
MB-MC Main belt - middle, comet behavior (coma and/or tail)
MB-O Main belt - outer
MB-OC Main belt - outer, comet behavior (coma and/or tail)
MC Mars crosser
NEA NEA (Apollo/Aten/Amor)
NEA-C NEA (Apollo/Aten/Amor), comet behavior (coma and/or tail)
NYSA Nysa
PHO Phocaea
THM Themis
TNO TNO/KBO
TR-J Trojan - Jupiter
TR-M Trojan - Mars
TR-N Trojan - Neptune
TR-S Trojan - Saturn
TR-U Trojan - Uranus
V Vestoid
See the discussion in 3.1.2, "Indirect Data".
GSOURCE (G = Phase Slope Parameter, SUMMARY)
--------------------------------------------
Blank None (assumed to be 0.15 in MPCORB)
D Default (assigned based the assumed value for a given taxonomic class)
L Taken from Details list entry
G G12 system
M MPCORB (usually 0.15)
GSOURCE (G = Phase Slope Parameter, DETAILS)
--------------------------------------------
Blank None (default = measured)
A Assumed (based on class, orbital group, etc.)
C Calculated
D Derived
G G12 system
M Measured
HBAND (H = absolute magnitude, standard filter)
-----------------------------------------------
Blank Assumed to be Johnson V
B Johnson Blue filter
V Johnson Visual filter.
R Red filter (presumed to be Cousins R, not Johnson R)
I IR filter (presumed to be Cousins I, not Johnson I)
SG SDSS g
SR SDSS r
SI SDSS i
HSOURCE (H = absolute magnitude, SUMMARY)
-----------------------------------------
Blank None or unknown.
A ASTORB file maintained by E. Bowell, Lowell Obs., Flagstaff
D Derived from reported Diameter and or albedo
E Estimated, e.g., derived from a "Bowell orbit" and assumed albedo
L Taken from Details list entry
M MPCORB file maintained by the Minor Planet Center