Asteroid taxonomic signatures from photometric phase curves

We explore the correlation between an asteroid's taxonomy and photometric phase curve using the H, G12 photometric phase function, with the shape of the phase function described by the single parameter G12. We explore the usability of G12 in taxonomic classification for individual objects, asteroid families, and dynamical groups. We conclude that the mean values of G12 for the considered taxonomic complexes are statistically different, and also discuss the overall shape of the G12 distribution for each taxonomic complex. Based on the values of G12 for about half a million asteroids, we compute the probabilities of C, S, and X complex membership for each asteroid. For an individual asteroid, these probabilities are rather evenly distributed over all of the complexes, thus preventing meaningful classification. We then present and discuss the G12 distributions for asteroid families, and predict the taxonomic complex preponderance for asteroid families given the distribution of G12 in each family. For certain asteroid families, the probabilistic prediction of taxonomic complex preponderance can clearly be made. The Nysa-Polana family shows two distinct regions in the proper element space with different G12 values dominating in each region. We conclude that the G12-based probabilistic distribution of taxonomic complexes through the main belt agrees with the general view of C complex asteroid proportion increasing towards the outer belt. We conclude that the G12 photometric parameter cannot be used in determining taxonomic complex for individual asteroids, but it can be utilized in the statistical treatment of asteroid families and different regions of the main asteroid belt.Comment: submitted to Icaru

UCOT: Semiautomatic Generation of Conceptual Models from Use Case Descriptions

This paper describes a prototype of a system to auto matically analyze use cases and create a conceptual model based on the analysis. Grammatical parser and Abbott’s heuristic are used to process the use cases. User can modify the conceptual model by refining entities and relations, as well as roles for the entities. The model can be exported to be further utilized with object oriented analysis or domain specific modeling. The system is evaluated based on the analysis of use cases used to describe the system itself. The quality of models depends essentially on the quality and writing conventions of the use cases. If the use cases are written using subject-predicate-object struc ture and usage of synonyms is minimized, then the system can produce appropriate conceptual model of the use cases, facilitating requirements analysis and domain engineering.peerReviewe