UU Aurigae

Abyss Odyssey

A
133091


UU Aurigae is a carbon star located in the Auriga constellation
Edmonton, Alberta, Canada
2017-Oct-12
Exposures: RGB 10/10/10 x 2m = 60m
Processing: SGP,MaximDL,Gimp
Telescope: CFF132,STF-8300M,GM1000
Guider: ST80,LodestarX2,GSO2X.


It seems that this star is still unattainable. The purpose of this object in the game is unclear.
I want to hear your opinion about this object.
Any idea...
 
Last edited by a moderator:
UU Aurigae is a carbon star located in the Auriga constellation
Edmonton, Alberta, Canada
2017-Oct-12
Just out of curiosity, is that your own picture/location?
If so, it's nice to see a fellow Edmontonian around these parts...err, forums!

Sorry nothing to really add to the topic, I have not investigated this star at all so I am unsure. Gives me something to do though so I may check it out and try to form some kind of theory.
 
View attachment 133091

UU Aurigae is a carbon star located in the Auriga constellation
Edmonton, Alberta, Canada
2017-Oct-12
Exposures: RGB 10/10/10 x 2m = 60m
Processing: SGP,MaximDL,Gimp
Telescope: CFF132,STF-8300M,GM1000
Guider: ST80,LodestarX2,GSO2X.


It seems that this star is still unattainable. The purpose of this object in the game is unclear.
I want to hear your opinion about this object.
Any idea...

Ask the Gnosis to pop out there and take look, you could hitch a ride with them!
 
Part of the problem here is that there's been a serious error in placing the star in the ED universe. They've put it about ten times further away that it should be - it's about 10,000 LY away from Earth while the best-guess estimates are that it's actually only about 1,000 LY from Earth. Looks like a decimal point transposition to me.

Too late to move it now, of course; dumping a new multiple-solar-mass star down in the general vicinity of Wregoe ZC-H b11-0 would completely disrupt the Stellar Forge calculations for the entire Wregoe sector.
 
Part of the problem here is that there's been a serious error in placing the star in the ED universe. They've put it about ten times further away that it should be - it's about 10,000 LY away from Earth while the best-guess estimates are that it's actually only about 1,000 LY from Earth. Looks like a decimal point transposition to me.

Too late to move it now, of course; dumping a new multiple-solar-mass star down in the general vicinity of Wregoe ZC-H b11-0 would completely disrupt the Stellar Forge calculations for the entire Wregoe sector.

However if they are using the Hipparcos 2007 star data which indicates a distance of 8583ly they have it right. I have seen other data that says 1,810ly and another 1,630, give or take around 10% so best guess is probably between 1k and 2kly.

What's happened is they have just imported the Hipparcos star catalogue in its entirety and that's the distance it is using in game.
 
So I guess ED is accurate to Hipparcos... but the question remains as to how precise Hipparcos is. ;):D

The Hipparcos data was reprocessed and revised in 2007 from the original data collection gathered in 1997. The distance of 1,812ly is actually from the same data collection, from when it was originally processed. In 2007 using better methods it was reprocessed and revised to give us the 8583ly distance. It should probably be taken as correct, until we get more accurate updated readings of course.

The revised versions is called the Hipparcos 2 catalogue to differentiate it from the original catalogue.
 
Part of the problem here is that there's been a serious error in placing the star in the ED universe. They've put it about ten times further away that it should be - it's about 10,000 LY away from Earth while the best-guess estimates are that it's actually only about 1,000 LY from Earth. Looks like a decimal point transposition to me.

Too late to move it now, of course; dumping a new multiple-solar-mass star down in the general vicinity of Wregoe ZC-H b11-0 would completely disrupt the Stellar Forge calculations for the entire Wregoe sector.
I write about this error in detail in this post (one of my first posts :D)

In a nutshell, the error appears to purely be due to the precision of the Hipparcos data and the way it is implemented in Elite Dangerous. As you well know, precision (in scientific measurement) is often quantified with a standard error range or confidence interval, i.e. those +- values you see next to the reported value. Hipparcos had a precision of around 1 milliarcsecond (mas for short) in their parallax. This is good for most objects within a couple thousand light years of Earth, since their parallax will be several mas or greater. But parallax has an inverse relation, and as the parallax approaches 0 mas, the distance the object is from Earth asymptotically approaches infinity. This is what happens with a few hundred of the stars in the HIP dataset, where their parallax is less than 1 mas.

1 arcsecond is 1 parsec distance or 3.26 ly
100 mas is 10 pc = 32.6 ly
10 mas is 100 pc = 326 ly
1 mas is 1000 pc = 3260 ly.
etc.

Some stars have reported values of nearly 0 mas, with a systematic error of 1 mas due to the limitations of Hipparcos mentioned earlier, but when these stars were imported to ED, they used the exact parallax value. Meaning, if a star had a value of 0.10 +-1 mas in the hipparcos catalog, it would apparently be 32600 ly away! We know in reality that the satellite could have no chance of detecting a perfectly normal star from that far away, so the error range is likely playing a factor, but the stars were imported with this distance nonetheless.

The cutoff for this is 0.07 mas = 46596 ly. Smaller parallax values appear to have been stripped out (or perhaps the developers blacklisted catalog stars further away than 50000 ly). Also note that negative parallax values in the set were completely excluded. In reality, this is just a technicality (the star moved left instead of right during the parallax measurement) and should have no difference, but half the stars in the catalog are not in Elite Dangerous because of this fact!

EDIT: just realized this is a thread from 2019...did not realize I was necroing
 
Last edited:
For those wondering where it is on the map, it's here. Doesn't look like it should be unreachable, but apparently it is?
It isn't reachable, because if it were someone would have been there by now! ;) It's only in EDSM because its coordinates were triangulated and reported before logs reported star coordinates. It's far above the galactic plane if memory serves correctly, and fleet carriers still can't reach it because no catalog stars are close enough to "bridge the gap".

And?

Does this information become less interesting because the original post was made in 2019? Why?

It is just bad forum manners to revive very old posts, that's all...
 
It is just bad forum manners to revive very old posts, that's all...
Says who?

I would have not known of this peculiar star system if this thread hadn't been "revived", and I find it utterly interesting. If people had just followed this completely made-up convention (which AFAIK isn't even a rule in these forums) I would have never found out. I don't see how this is "bad forum manners" or in any way a negative thing.

The whole concept of "necroposting" (as some kind of bad thing) is completely made-up . Where did you even learn of this "rule"?
 
The whole concept of "necroposting" (as some kind of bad thing) is completely made-up . Where did you even learn of this "rule"?
It really depends on the thread (and from observation, the mods lock or don't at discretion on that basis) rather than a general rule.

Something like this, it's not a problem. UU Aurigae hasn't changed since 2019 and is still unreachable.

If you resurrect some thread from 2019 on, say, Thargoids, or core mining, then people reading the first posts expecting them to be accurate to now are going to get very confused, because the forum software doesn't highlight "hey, this post is really old" - and indeed the posting dates are pretty de-emphasised in general - so all the early posts get a bunch of anachronistic "no, that's wrong" replies or similar.
A news thread talking about a June 2022 update got pulled back up recently and confused a few people because they assumed it was about some coming June 2023 update.
That sort of thing it's best to make a new thread on the same topic so you get current information rather than a mix of current and ancient with an unclear dividing line.
 
f you resurrect some thread from 2019 on, say, Thargoids, or core mining, then people reading the first posts expecting them to be accurate to now are going to get very confused, because the forum software doesn't highlight "hey, this post is really old" - and indeed the posting dates are pretty de-emphasised in general - so all the early posts get a bunch of anachronistic "no, that's wrong" replies or similar.
If that ends up happening (ie. someone responds to an old thread that contains obsolete information, and people are responding to the thread thinking that it's currently valid information and then finding out that oops, it's actually just a very old thread), perhaps then apologize for having misled people.

When it's this kind of thread which contains still-completely-valid information that's extremely interesting, there's literally no reason to apologize. Heck, I would like to thank Vilena Duval for bringing this tidbit to the limelight once again. It was very interesting!
 
Back
Top Bottom