Search results for query: meananomaly

That all looks like a match to me. The gravity is just in different units (this is a constant annoyance, actually) - on Spansh and Inara it's in units of Earth gravities, while in the journal it's in m/s/s, but only Inara actually mentions the units. (Nice one Artie!)

...}, "SemiMajorAxis":1347270846.366882, "Eccentricity":0.003216, "OrbitalInclination":0.643958, "Periapsis":340.377539, "OrbitalPeriod":68291.271925, "AscendingNode":-65.519908, "MeanAnomaly":71.839030, "RotationPeriod":68291.964923, "AxialTilt":0.399152, "WasDiscovered":true, "WasMapped":true }

..."OrbitalInclination":-0.096322, "Periapsis":323.076557, "OrbitalPeriod":749607777.595520, "AscendingNode":18.199459, "MeanAnomaly":129.489737, "RotationPeriod":55482.157477, "AxialTilt":-0.484607, "WasDiscovered":false, "WasMapped":false } Though I suppose the limitation is you have to have...

..."OrbitalInclination":0.011714, "Periapsis":220.725647, "OrbitalPeriod":4370443.284512, "AscendingNode":163.114889, "MeanAnomaly":188.225291, "RotationPeriod":4370519.902315, "AxialTilt":0.036380, "WasDiscovered":false, "WasMapped":false } The relevant log lines from visit 2 in log 2 are: {...

Not yet. Bad timing that I posted before going away for the week 😆

I think (though it's a guess) that the OP has now made it work. Meanwhile, the epoch for the data (the MeanAnomaly in other words) appears to be the timestamp of the line in the journal with the data - the MeanAnomaly changes each time.

...calculate the positions of bodies (but the formula should not include the longitude of ascending node or the argument of periapsis — just MeanAnomalyAtTimeOfCalculation = (MeanAnomalyFromScan + ((TimeOfCalculation - TimeOfScan) / OrbitalPeriod)*360) mod 360 will do). Oh, and there may be...

So you also need to calculate the MeanAnomaly for the same timestamp for all bodies. (MeanAnomaly + ([seconds between timestamp display and timestamp scanned] / OrbitalPeriod) * 360 - AscendingNode - Periapsis) mod 360

...between each body calculated using those XYZ coordinates. Name SemiMajorAxis Eccentricity OrbitalInclination AscendingNode Periapsis MeanAnomaly X coordinate Y coordinate Z coordinate Gludgoi JX-V b57-3 0 0 0 N/A 0 0 0.0 0.0 0.0 Gludgoi JX-V b57-3 1 144466292858.12378 0.000293 0.003815...

...you the search options dialog and let you create a new search with the same options): https://forums.frontier.co.uk/search/1030209/?q=meananomaly&o=date Potentially relevant threads included: https://forums.frontier.co.uk/threads/mattgs-observatory-plugins.589466/...

I think there's a good chance that all the data needed is now present. When I'm back on my PC in the morning I'll share the links to the posts I came across (not sure why you're not seeing them now) 👍👍

No it's there "AscendingNode" with a D... not AscendingNote :) The barycentre scans are what makes working out the xyz of other bodies a bit more challenging. Whilst I figure that moons orbiting are barycentre close enough together for the barycentre to be used for both moon locations, planet...

Hello @Cmdr Bolamshea , I don't understand too much about the whole story, but I find the idea quite exciting. My last scans are from 30.11.2024. In the event “(body) Scan detailed” and in the event “ScanBaryCentre” all variables are included in my last scans. I am attaching two journal entries...

...from 2018 and it looks like the "missing" information wasn't actually available then. I just looked at a log file from 2020 and May 2021 MeanAnomaly (the location of the body in the orbit) wasn't in scan data. A log from October 2021 though, this now exists. This is the same story with the...

Further to this, if you search the forum (I recommend doing so sorted by date) for "MeanAnomaly" then you'll find a number of threads which touch on the same topic. A few posts have hints that there are issues with the data (e.g. sign conventions and even meanings), and indeed hints that the...

..."Eccentricity":0.000000, "Orbitalclination":0.000000, "Periapsis":0.000000, "OrbitalPeriod":123112.136126, "AscendingNode":0.000000, "MeanAnomaly":284.985435, "WasDiscovered":false, "WasMapped":false } The closest thing to "ring composition" is the ring class, and that doesn't require...

Interesting custom criteria here. Ran my journals through it, and my closest was - 2017-09-03 01:59:38 Phraa Pruae CL-Y d2313 4 ELW Similarity Score Score: 6.10 What could also be interesting is ELW's that still classify as an ELW with the biggest difference. My biggest score is...

..."OrbitalInclination": 0.001306, "Periapsis": 19.018218, "OrbitalPeriod": 26545828.580856, "AscendingNode": 74.184877, "MeanAnomaly": 225.194909, "RotationPeriod": 80044.520763, "AxialTilt": -0.365010, "WasDiscovered": false, "WasMapped": false } Using your sheet, I can get...

Thank you very much for the part with Tionisla being related to Raxxla. When the galmap allowed us to look for any bodies (stars, planet, comets too!), i got the Tionisla system. I kept the signal sources to compare them later to identify the "NonBodyCount". NB: while i was copying it, i...

...In this particular case, I find no clear differences. Both FSS and DSS emit a 'Detailed" scan record, the only differences between which I am able to detect (using software comparer) concerns timestamp, DistanceFromArrivalLS and MeanAnomaly. I ignore timestamp. DistanceFromArrivalLS is...

My guess is you scanned A 5 c before A 5 and it was therefore unable to determine exactly where A 5 c was in the system so throws out the other variant as a possibility. By the time you'd mapped A 5 c, you'd since FSSed A 5 and it was then able to determine position and rule out other variant...

...{"timestamp":"2023-10-10T07:02:01Z","event":"FSSBodySignals","BodyName":"Pencil Sector HW-W c1-5 A 5 c","BodyID":47,"SystemAddress":1459651351242,"Signals":[{"Type":"$SAA_SignalType_Biological;","Type_Localised":"Biological","Count":2}]}

..."Eccentricity":0.000000, "Orbitalclination":-84.428132, "Periapsis":276.322819, "OrbitalPeriod":34699.093699, "AscendingNode":42.854922, "MeanAnomaly":220.999145, "RotationPeriod":35142.484890, "AxialTilt":-0.522399, "WasDiscovered":true, "WasMapped":true } {...

..."OrbitalInclination":0.015357, "Periapsis":119.259812, "OrbitalPeriod":272750.198841, "AscendingNode":-136.420256, "MeanAnomaly":53.468709, "RotationPeriod":272758.710211, "AxialTilt":-0.315566, "WasDiscovered":false, "WasMapped":false } { "timestamp":"2023-05-12T20:48:51Z"...

Thanks for this, and especially providing journal entries. As others have noted, in some cases I also need details on star types but in this instance it's because of the atmosphere type not being one of the expected ones - don't recall seeing Tectonicas on an Argon-Rich body before. I'll get it...

..."OrbitalInclination":-0.568850, "Periapsis":227.498254, "OrbitalPeriod":22321251.034737, "AscendingNode":110.091240, "MeanAnomaly":120.022181, "RotationPeriod":99476.889888, "AxialTilt":0.050283, "WasDiscovered":false, "WasMapped":false } Please let me know if you require other...

To my surprise there is nothing in the logs - I didnt know this. I looked at my logs when I probed Delphi 5a (thargoid base) but there is nothing. After that I sold my current exploration data and went on a detour to HIP 19026 specifically to get the data. Again nothing... scatches head they are...

..."OrbitalInclination":50.896557, "Periapsis":3.460239, "OrbitalPeriod":3446406781.673431, "AscendingNode":104.326058, "MeanAnomaly":59.048601, "RotationPeriod":194667.460496, "AxialTilt":0.000000, "Rings":[ { "Name":"Smojai RM-O c8-0 A A Belt", "RingClass":"eRingClass_MetalRich"...

I linked a beta version a while back you need to be trying - here. Before installing it, it might be worth deleting your BioInsights.log as well, so we only capture recent details.

..."OrbitalInclination":0.546433, "Periapsis":204.820967, "OrbitalPeriod":125678145.885468, "AscendingNode":129.118521, "MeanAnomaly":251.634722, "RotationPeriod":76320.548161, "AxialTilt":0.148991, "WasDiscovered":false, "WasMapped":false } 28-Dec-2022 06:48:28.066759 Object reference not set...

..."OrbitalInclination":-0.823433, "Periapsis":335.314914, "OrbitalPeriod":84672901.630402, "AscendingNode":-75.707323, "MeanAnomaly":89.492717, "RotationPeriod":141119.730365, "AxialTilt":-0.371548, "WasDiscovered":true, "WasMapped":true } 13-Dec-2022 19:29:23.407416 Object reference not set to...

...} "SemiMajorAxis":1312000870.704651 "Eccentricity":0.000000 "OrbitalInclination":-0.282251 "Periapsis":261.644326 "OrbitalPeriod":16007354.855537 "AscendingNode":100.759914 "MeanAnomaly":252.651077 "RotationPeriod":4154463.229419 "AxialTilt":0.231440 "WasDiscovered":true "WasMapped":false

The screenshot from my app was from my odyssey commander as were the logs. The third pic is the only one from the horizons commander. As for the wasmapped being false, that's just ED being ED. My app calculated the values from the Autoscan event which indeed has the wasmapped as true. The...

I have an alt which doesn't have Odyssey. I'll see what the payouts are. I did notice though that if you load in 4.0, the fileheader event states odyssey as true while the loadgame event has horizons as true and odyssey false. EDIT: Ok, I mapped an ELW and WW. Odyssey logs Value in game...

OK, here are the results of my first test. This is a system that has been fully scanned and mapped by other people. I started after the autoscan that happens when you jump into a system... This all seems to be working as I would expect. This is quite close to the bubble, so I'll see if I can...

Never mind.It looks like it is an issue with the update time on spansh being changed when the meanAnomaly is not sent by some clients so I don't have a reliable epoch. This is why my code is only accurate 50% of the time!

..."Eccentricity":0.014562, "OrbitalInclination":0.196286, "Periapsis":42.518979, "OrbitalPeriod":157907.092571, "AscendingNode":1.964940, "MeanAnomaly":182.570428, "RotationPeriod":-157912.682654, "AxialTilt":2.446658, "WasDiscovered":true, "WasMapped":true } Journal.220311140639.01.log:{...

...pulled together a list of bodies that can potentially have collisions. Most of these systems need to be rescanned so that we can get the meanAnomaly from the journal and this will allow us to calculate the date, time and duration of the collisions. I'll be periodically updating the list, and...

...If you want the actual current mean anomaly, it can be advanced by a number of degrees based on elapsed time and the orbital period (meanAnomaly += 360*days/period). So starting with that Mean Anomaly, we have to first get the Eccentric Anomaly. This is the complicated part. There's no...

...of death. If it was days I would move on. If just hours I would carry on my way. According to the journal at 2022-04-07 14:36:24 the meanAnomaly of AB 1 was 335.894091 degrees which is essentially the number of degrees it has orbited since the last periapsis (closest approach). So this...