Re: 1st Call for Observations - It’s Time for Testing Orbit Determination with visual Observation

From: Andreas Hornig via Seesat-l <seesat-l_at_satobs.org>
Date: Fri, 27 Jul 2018 21:38:37 +0200
Hi Brad,

I am that Andreas from the second name under Jorge's email.
So i can also answer some of your questions :).

On Fri, Jul 27, 2018 at 9:12 PM Brad Young via Seesat-l <seesat-l_at_satobs.org>
wrote:

> Jorge,
> I would like to help with this – but I have a few questions that may be of
> general interest so I posted to the list. This is not a qualification list,
> but more a wish list to borrow your phrase:
> I assume we would continue to use seesat to post our observations, and our
> normal format?
>

Yes!
1. we wan't to test our code with the formats you use here.
2. we also want you to publish it as you use to via this email list.

so no special treatment for us and full visibility as usually.
In the end, we want you to use the software as easily as possible.


> Will your product be open source?
>

The code is already:
https://github.com/aerospaceresearch/orbitdeterminator/blob/master/LICENSE
if you define "product" also the result of our call for observations here,
yes. See also next point.


> Please clarify what you mean by “we will provide our results back to the
> community“ – do you mean a summary report, are you going to provide a
> product we could use?
>

We do this because we want others to use it. This is why our first step is
to publish the outcome based on your inputs here, too. That is just fair!
Next step is to see if you can use it. We are looking for your comments
then and try to implement them then.

What we will do is to post:
the orbital parameters we generated.
compare them to TLEs of the same satellites for residuals.
write a small report of some kind.
if you want to know more, we invite you to suggest something you will be
interested in then.


> What will be the output of the program? A two line elements set, state
> vectors, simple sightings prediction, or other data?
>

orbital parameters.
The test will help us to get into the direction of TLEs. But as it is
always said, TLEs are hard to do. This is why we do tests for now.
With the orbital parameters, we will try to predict the satellite's
position, and validate then.


> The rest of the questions only apply if it is actually modifiable to suit
> observational fitting (unlike say elfit or other extant programs):
> Will your product be constructed so that it is using standard orbital
> determination models (SGP, SDP etc.)?
> Will perturbation parameters be tunable? I’m not a programmer, but I’m
> assuming that there will be some sort of goal seek or other simple
> algorithm that a more general audience could use?
>

There, I need to ask the others (Alexandros, Nilesh, Arya and Aakash).
I am mentoring just Jorge and we concentrated on the bringing other
"measurements". But I saw the others work on SGP4[0]

[0]
https://github.com/aerospaceresearch/orbitdeterminator/commit/e65f509d72f6f80156d15548b3127b4603b3136e

More questions? :)

Andreas
_______________________________________________
Seesat-l mailing list
http://mailman.satobs.org/mailman/listinfo/seesat-l
Received on Fri Jul 27 2018 - 14:39:43 UTC

This archive was generated by hypermail 2.3.0 : Fri Jul 27 2018 - 19:39:43 UTC