View Issue Details

IDProjectCategoryView StatusLast Update
0001390SkyChart1-Softwarepublic15-02-05 13:04
Reporteruser116Assigned ToPatrick Chevalley  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Platformx86OSWindowsOS VersionXP
Product Version3.11 SVN 
Target Version4.0Fixed in Version3.11 SVN 
Summary0001390: Manually entered orbital asteroid elemets do not work
DescriptionSolar System
 - Asteroid
 -- Add

Elements are accepted with "Ok" message but asteroid cannot be found when searched. The program simply does not respond (I set magnitude limit to 99 to be sure it would show up)

Also, where and which file are the new asteroid elements are supposed to be stored?
Steps To ReproduceSee screen shot of panel
TagsNo tags attached.

Activities

user116

15-02-05 00:40

 

Patrick Chevalley

15-02-05 13:04

administrator   ~0002989

This is fixed by revision 3075:
http://sourceforge.net/p/skychart/code/3075/

The problem is because of the extra digits for the Epoch, generally the asteroid elements are for 0h UT so the digit is only .5
If you set the epoch as 2455872.7 it work without the fix.

The elements are stored in the SQLite database located in C:\Documents and Settings\[user]\local Settings\Application Data\Skychart\database\cdc.db
You can browse the database content with a database manager software like sqliteman: http://sqliteman.yarpen.cz/
The asteroids elements are in the table cdc_ast_elem.

Avoid to use an existing asteroid number for the designation, 10000 can conflict with "10000 Myriostos".
I suggest starting at 999001 for this kind of objects.





Issue History

Date Modified Username Field Change
15-02-05 00:40 user116 New Issue
15-02-05 00:40 user116 File Added: Asteroid elements manual entry.jpg
15-02-05 10:06 Patrick Chevalley Assigned To => Patrick Chevalley
15-02-05 10:06 Patrick Chevalley Status new => confirmed
15-02-05 10:06 Patrick Chevalley Target Version 0.3.0 => 4.0
15-02-05 13:04 Patrick Chevalley Note Added: 0002989
15-02-05 13:04 Patrick Chevalley Status confirmed => resolved
15-02-05 13:04 Patrick Chevalley Resolution open => fixed
15-02-05 13:04 Patrick Chevalley Fixed in Version 0.3.0 => 3.11 SVN