RE: DCB Obs FEB 27th UT - ORS-1 / NOSS 2-1 Trio / DMSP F18

From: Derek C Breit (breit_ideas@poyntsource.com)
Date: Wed Feb 27 2013 - 18:35:25 UTC

  • Next message: C. Bassa: "CB Obs February 27, 2013"

    C.2  Using ObsReduce Without Orbital Elements 
    
    If you do not have orbital elements for an object, or prefer not to use
    them, ObsReduce can still help reduce your stars, as long as you know their
    approximate coordinates. 
    
    - select observation site 
    
    - enter Desig 
    
    - IOD users must enter SSN 
    
    
    
    
    No where does it explain how to enter an UNID..
    
    But I must run away for today, so I will use the data I have and try putting
    99999 in the Desig, or the SSN, or both and see what happens..
    
    Derek
    
    -----Original Message-----
    From: seesat-l-bounces+breit_ideas=poyntsource.com@satobs.org
    [mailto:seesat-l-bounces+breit_ideas=poyntsource.com@satobs.org] On Behalf
    Of Derek C Breit
    Sent: Wednesday, February 27, 2013 10:19 AM
    To: 'C. Bassa'
    Cc: 'Seesat List'
    Subject: RE: DCB Obs FEB 27th UT - ORS-1 / NOSS 2-1 Trio / DMSP F18
    
    
    Thanks.. 
    
    C1.2 says I still have to enter a sat ID..  It's the "must enter SSN" that
    hangs me up.. I remember I tried 99999 *once* way back when and it didn't
    like it much..
    
    Of course, I have never read the manual, so I have some reading to do..
    
    Derek
    
    
    -----Original Message-----
    From: C. Bassa [mailto:cgbsat@gmail.com] 
    Sent: Wednesday, February 27, 2013 10:09 AM
    To: Derek C Breit
    Cc: Seesat List
    Subject: Re: DCB Obs FEB 27th UT - ORS-1 / NOSS 2-1 Trio / DMSP F18
    
    Hi Derek,
    
    On Wed, Feb 27, 2013 at 5:42 PM, Derek C Breit
    <breit_ideas@poyntsource.com> wrote:
    > I have an UNID flasher running same direction (but seriously off track and
    > 30 seconds later)as #1668 near Procyon moments before DMSP F18. It
    Appulsed
    > 8 CMi /SAO 115610 at (J2000) RA 07 33 11.6 Dec 03 17 25.0 at a UT time of
    > 03h 33m 44.996s. 11 Flashes over around 30 seconds.. If anyone thinks it's
    > important, I can determine a second point, but I still can't do an UNID in
    > Obsreduce.. Don't know how..
    
    That time and position match an ATLAS CENTAUR R/B [06797/73058B]. It
    was moving almost due East, which approximately matches the direction
    of 01668.
    
    As for using ObsReduce on unknown, check section C1.2 in the ObsReduce
    manual (http://www.satobs.org/programs/ObsReduce/ReadMe.html). Given
    that 06797 is a good match, you can use ObsReduce like you normally
    do, then try the steps from C1.2.
    
    Regards,
        Cees
    -----
    No virus found in this message.
    Checked by AVG - www.avg.com
    Version: 2013.0.2899 / Virus Database: 2641/6134 - Release Date: 02/26/13
    
    _______________________________________________
    Seesat-l mailing list
    http://mailman.satobs.org/mailman/listinfo/seesat-l
    -----
    No virus found in this message.
    Checked by AVG - www.avg.com
    Version: 2013.0.2899 / Virus Database: 2641/6134 - Release Date: 02/26/13
    
    _______________________________________________
    Seesat-l mailing list
    http://mailman.satobs.org/mailman/listinfo/seesat-l
    



    This archive was generated by hypermail 2b29 : Wed Feb 27 2013 - 18:36:04 UTC