<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>All right :).</p>
<p>When I download all neos, the file is like 500K. Should I do a
separate download for the NEOs (without magnitude filter) as well?</p>
Cheers. And thanks for the feedback.<br>
<br>
Valentin.<br>
<br>
<div class="moz-cite-prefix">On 03/18/2017 09:49 PM, Jasem Mutlaq
wrote:<br>
</div>
<blockquote
cite="mid:CAE0bU5=6yDWBFZ92AYiYfx4WzzBWmm9cYdPd5qP75fKa4ShCqg@mail.gmail.com"
type="cite">
<div dir="ltr">Hi Valentin,
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Jasem</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, Mar 18, 2017 at 5:29 AM,
Valentin Boettcher <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:valentin@boettcher.cf"
target="_blank">valentin@boettcher.cf</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Edit: <br>
</p>
<p>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. <br>
</p>
<p>I alter the first query, so that no NEOs are returned
to avoid dublication.</p>
<p>Cheers.<br>
</p>
<div>
<div class="h5">
<div class="m_-2674300053446667438moz-cite-prefix">On
03/18/2017 02:37 PM, Valentin Boettcher wrote:<br>
</div>
<blockquote type="cite"> Hello all.<br>
<br>
I've just got into KStars development and took on
the junior job "Investigate NEOs".<br>
<br>
Here are my results:<br>
<br>
I've constructed a request to JPL myself and got out
a csv of several hundred megabytes, which is
certainly not suitable for KStars.<br>
<br>
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.<br>
<br>
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'.<br>
<br>
The asteroid (2003 YT1) with an absolute magnitude
of 16.2 doesn't mach the criteria and is not
included in the download.<br>
<br>
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.<br>
<br>
One/I could maybe implement a setting for the
absolute magnitude filter, to leave it to the user.<br>
<br>
I am looking forward to feedback! (Maybe I haven't
understood it...)<br>
<br>
Cheers and Thanks!<br>
<br>
Valentin Boettcher (hiro, hiro98)<br>
<br>
<br>
P.S. Here is a screenshot with 2003 YT1 :). KStars
crashed after a while...<br>
<br>
<img src="cid:part2.4AE50F26.977FF802@boettcher.cf"
alt=""> </blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div>Best Regards,<br>
Jasem Mutlaq<br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>