1) Series of plots made from following orbit elements for the sungrazer:

from JPL Horizons:
	 https://ssd.jpl.nasa.gov/tools/sbdb_lookup.html#/?sstr=C%2F2024%20S1
	(2024-Oct-26 00:12:23 solution date)

	Nominal value			1-sigma uncertainties	units
    2024-Oct-28.48546468 TDB			.00030554	days
    q: 0.007947318867201049			2.6922E-6	AU
    e: 0.9999179532701665			3.729E-6	-
    i: 141.8986575995367			.0030645	deg			
    Node: 347.1268713008016			.021313		deg
    Peri: 69.14814504105068			.018722		deg

I use those orbit elements to generate SPICE SPK files.
Then use SPICE light travel equation solving to compute ephemerides as perceived by various observing platforms.
Then use a home-brewed coordinate transformation into HPC (Helioprojective longitude/latitude).
NB: I use Space-Track.org TLEs to generate SPK files for LEO spacecrafts and SDO.


2) <observer>.png files:

Blue asterisk marks the perihelion.
Blue crosses are hour markers before/after perihelion.
Black trajetory line indicates sungrazer is closer to observer than Sun center.
Light gray trajectory line: sungrazer is further away than Sun center.

Files ending with _MC00100.png or _MC01000.png refer to plots where 100 or 1000 additional trajectories were superposed, 
each trajectory varying from the nominal one by changing the nominal orbit elements by their 1-sigma error bars times a normally distributed random number
(Monte-Carlo approach).

3) <observer>.txt files:
Contains ephemeris (in usual helioprojective coordinates) from <observer>, 
with UTC time tags being as perceived by observer, i.e. corrected for light travel time.

4) <observer>.idlsave files:
IDL SAVE files containing same information as <observer>.txt files.
In IDL, use RESTORE command to read.