Junior Job: Investigate NEOs

[Valentin Boettcher]

All right :).

When I download all neos, the file is like 500K. Should I do a separate
download for the NEOs (without magnitude filter) as well?

Cheers. And thanks for the feedback.

Valentin.

On 03/18/2017 09:49 PM, Jasem Mutlaq wrote:
> Hi Valentin,
>
> Yes that could be a good compromise. I knew the file was pretty large,
> but I think we should introduce an option to set the magnitude and
> warn the users that file size can be quite large beyond a certain
> magnitude. We should have the default as a sane value for us. Looking
> forward to the patch.
>
> Regards,
> Jasem
>
>
> On Sat, Mar 18, 2017 at 5:29 AM, Valentin Boettcher
> <valentin at boettcher.cf <mailto:valentin at boettcher.cf>> wrote:
>
>     Edit:
>
>     An option would be to perform a separate query for the NEOs with
>     the parameters c1_item=Ag&c1_op==&c1_value=Y. The resulting CSV is
>     539K big and could be appended to the asteroids file. I will
>     implement a patch for that.
>
>     I alter the first query, so that no NEOs are returned to avoid
>     dublication.
>
>     Cheers.
>
>     On 03/18/2017 02:37 PM, Valentin Boettcher wrote:
>>     Hello all.
>>
>>     I've just got into KStars development and took on the junior job
>>     "Investigate NEOs".
>>
>>     Here are my results:
>>
>>     I've constructed a request to JPL myself and got out a csv of
>>     several hundred megabytes, which is certainly not suitable for
>>     KStars.
>>
>>     Looking at the differences between my query and the one in
>>     KStars, I found some extra parameters, which had not been
>>     included in my one: c1_item=Ai and c1_op=%3C and c1_value=12.
>>
>>     That basicly means, that JPL filters the asteroids for the ones
>>     which have an parameter 'H' (absolute magnitude) smaller than 12,
>>     which means that they are 'visible'.
>>
>>     The asteroid (2003 YT1) with an absolute magnitude of 16.2
>>     doesn't mach the criteria and is not included in the download.
>>
>>     The parameter can't be set much higher, because the file size of
>>     the download would increase rapidly and slow down KStars. I
>>     tested a magnitude of 17 with a file size of a bit over 78
>>     megabyte and my laptop struggled.
>>
>>     One/I could maybe implement a setting for the absolute magnitude
>>     filter, to leave it to the user.
>>
>>     I am looking forward to feedback! (Maybe I haven't understood it...)
>>
>>     Cheers and Thanks!
>>
>>     Valentin Boettcher (hiro, hiro98)
>>
>>
>>     P.S. Here is a screenshot with 2003 YT1 :). KStars crashed after
>>     a while...
>>
>
>
>
>
> -- 
> Best Regards,
> Jasem Mutlaq
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kstars-devel/attachments/20170318/d1748895/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 280503 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kstars-devel/attachments/20170318/d1748895/attachment-0001.png>