Hi,
As I explained in the attached message sent February, 19th to this
mailing list, I cannot do anything with this issue. At the moment
this comet is the only one with this problem.
When I used the orbital elements from MPC the problem is not
present. If I try to use the orbital elements from JPL/Horizons then
the issue arise.
I will release a new set of events for CometOcc, all with JPL
orbital elements but C/2021 P4. I will use MPC orbital elements for
it.
But this is a workaround, we need the help of Dave and Hristo in
order to solve it.
Hristo P., is it possible to delete the events of this comet?
Dave H., could you check what could be the root cause of this issue?
The main difference I can see between both orbital elements is in
the Mean Anomaly parameter.
Regards,
Carlos
El 28/02/2022 a las 20:29, Chris
Anderson via groups.io escribi¨®:
toggle quoted message
Show quoted text
All:
?
I don¡¯t recall seeing anything about this,
but looking at an event in OW for C/2021 P4 (Atlas) on 04
March 2022, there appears to be an error in the orbital
elements for this comet.? What caught my eye first was that
the comet¡¯s magnitude in OW is listed as 4.8, but digging a
bit more revealed that the orbit semi-major axis listed in OW
is 1.08045 AU, which would give the comet an orbital period of
just over one year.? Checking against the published orbital
elements, it looks like the perihelion distance was
inadvertently used for the semi-major axis value.? (Also, OW
has the comet¡¯s mean anomaly listed as ¡°0.¡±)? The effect of
all this is that OW thinks the comet¡¯s going to be occulting a
star in Virgo on 04 March, when it will actually be in the
vicinity of the Cassiopeia/Andromeda border.
?
So, hopefully Carlos Perell¨® (who maintains
the COMETOCC feed) is on this listserve, and can take a look
at this error.
?
Chris Anderson, Coordinator (he/him/his)
Centennial Observatory
Herrett Center for Arts & Science
College of Southern Idaho
Twin Falls, Idaho, USA
(208) 732-6663
canderson@...
?
Carlos Perell¨®