Re: [Celestia-developers] Component designations in the HD cross-index

[Chris L. <cl...@gm...>]

On Fri, Aug 29, 2008 at 3:41 AM, Andrew Tribick
<ajt...@go...> wrote:
> Ok, the constant idea makes sense. It might make things simpler for
> people using the cross-indices if the value is a power of ten, so it
> might be sensible to choose 1e6 instead of 359803.

Good idea . . .  it would make things more comprehensible if we ever
have to look at a cross-index entry in the debugger.

> One thing I haven't
> tested is how this code interacts with scripts, if one of the resident
> scripting gurus would be willing to test this that would be good.

I should have time today to look at this.

> I don't think we need to do it for SAO, since SIMBAD does not appear
> to list any designations with component IDs, however if we decide to
> implement other catalogs in future (e.g. Durchmusterungs, HR, GJ) we
> should probably build in this feature from the start.

OK.

--Chris

>
> Andrew
>
> 2008/8/29 Chris Laurel <cl...@gm...>:
>> Andrew,
>>
>> This looks like a good patch to me. The only suggestion that I have
>> for the code is to clarify things a bit by defining constant called
>> HDCatalogMax instead of using the literal value 359803 throughout.
>>
>> Do we need eventually need to adopt a similar approach for other cross indexes?
>>
>> --Chris
>>
>> On Wed, Aug 27, 2008 at 7:07 AM, Andrew Tribick
>> <ajt...@go...> wrote:
>>> I've implemented component designations in the HD cross-index, so that
>>> designations e.g. HD 178911 B can be used.
>>>
>>> The format of the hdxindex.dat file is thus slightly different: a
>>> value of (component id)*359083 is added to the HD number, where
>>> (component id) is zero for no component id, 1 for the A component, 2
>>> for the B component, etc. The value of 359083 is chosen because this
>>> is the highest HD number according to SIMBAD, and HD 0 is not used.
>>>
>>> This required some modifications in stardb.cpp, I have tested the
>>> basics in the modified file: the on-screen display shows the
>>> designation correctly, the component designations appear to resolve
>>> correctly in .ssc files and the OrbitBarycenter statement. I've only
>>> done this testing in the Windows interface so far, so further testing
>>> would be welcome.
>>>
>>> The archive contains the modified stardb.cpp file and an hdxindex.dat
>>> generated from SIMBATCH data which incorporates component
>>> designations.
>>>
>>> http://www.celestialmatters.org/users/ajtribick/hdpatch.zip
>>>
>>> Andrew
>>>
>>> -------------------------------------------------------------------------
>>> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>>> Build the coolest Linux based applications with Moblin SDK & win great prizes
>>> Grand prize is a trip for two to an Open Source event anywhere in the world
>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>> _______________________________________________
>>> Celestia-developers mailing list
>>> Cel...@li...
>>> https://lists.sourceforge.net/lists/listinfo/celestia-developers
>>>
>>
>