Re: [Gpredict-discussion] Clearing Local Database?

[Charles S. <ham...@gm...>]

As an FYI: PROITERES is now correctly labeled from celestrak.  If you
run older versions you might need to run --clean-tle and reload the
tles to get that name to appear.  With 1.4, now in beta is should
appear automatically.

Charles


On Tue, Sep 11, 2012 at 12:39 PM, Gus 8P6SM <8p...@an...> wrote:
> On 09/10/2012 04:44 PM, Alexandru Csete wrote:
>> On Mon, Sep 10, 2012 at 9:41 PM, Gus 8P6SM<8p...@an...>  wrote:
>>> Ok, here is what I did:
>>>
>>> 1)  Went to "Files to fetch" and removed all files.  Then added a file
>>> called "my_selection.txt" as the ONLY file listed.  Saved.
>>>
>>> 2)  Stopped Gpredict and made sure it was not running.
>>>
>>> 3)  Removed ~/.config/Gpredict/satdata and all contents.
>>>
>>> 4)  Created a folder called ~/Keps containing a file named
>>> "my_selection.txt" which contains TLEs for seven (7) only satellites of
>>> interest.  Six formerly known satellites and a new launch (PROITERES).
>>>
>>> 5)  Restarted Gpredict which immediately re-created
>>> ~/.config/Gpredict/satdata and placed 1,260 .sat files and 34 .cat files
>>> in it.  Where did these come from?
>>
>> These came from the distributed Gpredict package and are considered
>> part of the application data (whether you like it or not ;-)
>> What you experience is basically the same as when a new user starts gpredict.
>>
>>> 6)  Stopped Gpredict again, deleted ~/.config/Gpredict/satdata again,
>>> restarted with the --clean-tle command line option.  Result:  1,260 .sat
>>> files and 34 .cat files re-created again.
>>
>> You can do it as many times as you wish, gpredict will recreate the
>> local copy of the database thinking that either you are a new user or
>> that there are new satellites that you do not have.
>>
>>> 7)  Edit->Update TLEs-> From local files.  Point to my own ~/Keps
>>> directory.  Updated:6, Skipped:0, Missing:1,254, New:0. If there are
>>> seven TLEs in the file, how can it update only six, and yet skip none?
>>
>> Skipped means that the existing data is already as new as the new
>> data. If gpredict only updates 6 out of 7 satellites, it means that
>> the 7th data set is incorrectly formatted or the checksum is wrong.
>> Note that TLEs for new launches come often without checksum.
>>
>>> Net result:  I have 1,260 satellites in my local database, only 6 of
>>> which are of any current interest to me.  I simply CAN NOT get rid of
>>> the unwanted 1,254 satellites.  And more importantly I simply CAN NOT
>>> get the software to recognize (and therefore track) the newly launched
>>> PROITERES satellite.
>>
>> As I mentioned above, the data is probably incorrectly formatted. You
>> can check the log to see if there are any error messages.
>>
>>> Can anyone explain how I can:
>>>
>>> #1 Manage the local database so that it contains only satellites of
>>> interest to me, and NOT the 18,000% extra satellites that I have no
>>> interest in, which Gpredict seems to think I should know about?
>>
>> The short answer is that it is not possible because the data is part
>> of the application. Without that data the application may malfunction.
>>
>> The long answer is that it is possible but you have to modify the
>> database included with gpredict. Assuming that you have gpredict 1.3
>> installed from a binary package on linux (I'm only guessing since you
>> have not provided any info about your OS or gpredcit version), the
>> data is located in:
>>
>> /usr/share/gpredict/data/satdata/
>>
>> Basically, you need to crate a satellites.dat file and at least one
>> .cat file listing your satellites. All files are plain text and if you
>> only have 6 satellites you may as well edit it by hand. For larger
>> databases there are scripts in the source tree to create the database.
>> When you have created a satellites.dat file you also need to modify
>>
>> /usr/share/gpredict/data/Amateur.mod
>>
>> to only list satellites that you have.
>> When done you can wipe all your ~/.config/Gpredict to start from
>> scratch, then cross your fingers.
>>
>> I have no idea if this will work - I have just written this up from
>> how I recall gpredict should work. If it actually works, go quickly
>> and modify the "Update TLE" settings to prevent gpredict from
>> downloading the database again.
>>
>> Needless to say, you will have to redo this every time you upgrade
>> gpredict, because with every new gpredict a new database will be
>> installed.
>>
>> I would really like to understand why it is such a big deal to have
>> 1260 satellites in the database? Are you having a real problem or are
>> they just hurting your eye? Maybe you haven't discovered the the group
>> filtering and searching functionality in the module editor???
>>
>> I think most people are only interested in a handful of satellites but
>> I have never seen anyone being so determined about wiping the database
>> :-)
>>
>>> #2 Get Gpredict to accept that there has been a new launch, and that I
>>> want to track a satellite that is NOT already in it's list of known
>>> satellites?
>>
>> Actually, Gpredict will fetch new satellites automatically as soon as
>> they appear on Celestrak. If you have TLE from other source before
>> celestrak has them you can add them as you did, but the data must have
>> the correct format and with correct checksum.
>>
>> Alex
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Gpredict-discussion mailing list
>> Gpr...@li...
>> https://lists.sourceforge.net/lists/listinfo/gpredict-discussion
>>
>>
>
> Thanks for your explanation on how I might purge the database of
> unwanted entries.  It isn't really a 'big deal' to purge them.  My
> primary concern was to figure out how to get new satellites IN, not how
> to get old ones OUT.  But with your explanation, I now have an idea what
> is involved.
>
> But I figured that to solve my problem, I would simplify my own
> installation as much as possible, and purging a hundred dozen
> unnecessary satellites seemed like a good thing to do.  I looked for a
> way and couldn't find it.
>
> I simply COULD NOT BELIEVE that the software designers expected all
> users to live happily ever after with an immutable list of satellites
> permanently stuck in the database.  (Frankly, I'm still having a hard
> time believing it.  It's like buying a new iPod and finding that it
> contains 10,000 Country 'n' Western songs that you can't delete.)
>
> So, I figured there must be a way to do this, but I couldn't figure out
> how.   Therefore, with frustration peaking, I asked on the list.
>
> --
> 73, de Gus 8P6SM
> The Easternmost Isle
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Gpredict-discussion mailing list
> Gpr...@li...
> https://lists.sourceforge.net/lists/listinfo/gpredict-discussion