Hello Exoplanetaryscience,
I undid your revision 827536200 of Resonant trans-Neptunian object. The object you added, 2014 OJ394, is listed by the relevant source as a SDO (i.e., the resonance is not proven). Of course there might be references published since the last revision of that source (30 December, 2017). If you have such a reference, and the status of the object has been clarified, it should be okay to add it back to the list (including the reference). Alternatively, given the large size of the object, it could be added to the section of possible, unproven resonances (if there is a reference).--Renerpho (talk) 10:37, 25 February 2018 (UTC)[reply]
Hey there. I don't have a source as I assumed that a possible orbital resonance would fall under a routine calculation. I wasn't aware the section was for confirmed resonances. I suppose I could go write a paper on orbital dynamics of the various objects if you'd like, though. 10:51, 25 February 2018 (UTC)
A possible resonance (like, for the nominal orbit) is easy to show, and indeed is a routine calculation. To show that the entire uncertainty region lies inside the resonance is more difficult. If you know of unconfirmed resonances where the uncertainty region (not just the nominal orbit) is small enough to actually pin down the resonance, go ahead, write a paper and get it peer-reviewed! But don't do it just because you want to have it on Wikipedia. ;-) --Renerpho (talk) 23:57, 25 February 2018 (UTC)[reply]
Buie does not show a resonance for 14OJ394. -- Kheider (talk) 00:40, 26 February 2018 (UTC)[reply]
Thanks, that confirms that there is indeed no possibility of resonance (it's not just not proven, it's ruled out).--Renerpho (talk) 12:36, 26 February 2018 (UTC)[reply]
Please join us from 10:00 am - 5:00 pm on Saturday, March 31st for Wikipedia Day LA 2018 at the Ace Hotel in downtown Los Angeles. There will be speakers, panel discussions, a presentation on Wikidata, flash sessions, and a discussion about the formation of an LA User Group. There could be dramatic readings of LA-related talk pages, and there will be truly excellent cake. Please RSVP on the event page if you're thinking of joining us.
Join our Facebook group here, and follow us on Twitter .
To opt out of future mailings about LA meetups, please remove your name from this list.
V774104 vs. 2015 TH367
@Exoplanetaryscience: I notice you have moved V774104 to 2015 TH367, and give a private email by David Tholen as the source. Can you explain the following statement from Scott Sheppard (January 2018):
“We just observed the object again a few weeks ago to solidify its orbit. The object is not the most distant object known, but it is only the third known object to have a large semi-major axis (greater than 150 AU) and a perihelion well beyond the Kuiper Belt edge, of which the other two are 2012 VP113 and Sedna.”
I'm not sure how this is supposed to make any sense, but david tholen I would trust to be reliable as one of the discoverers. Frankly, I'm just as confused on it as you are. There could be a chance they have astrometry still not yet submitted to the minor planet center... exoplanetaryscience (talk) 17:40, 14 March 2018 (UTC)[reply]
At least one of the discoverers is mistaken. Which is fine - they are only human. Who is right is hard to tell without solid evidence, but right now Sheppard is the only one who's statement is public and so I tend to believe him. An email is not enough unless David Tholen is willing to publish it rather than talk to you in private. If he does then we can add a note to the article, explaining that there is conflicting information. I am quite confident that 2015 TH367 is not V774104 (which was one of their brighter discoveries, see the discovery images[1]), whereas 2015 TH367 was at the very limit of what they could detect. It may have been the faintest object they have submitted during the entire survey. Let's wait for information that is publically available. Private emails should never serve as the only verification for an important claim on Wikipedia.--Renerpho (talk) 18:57, 14 March 2018 (UTC)[reply]
Also, note that 2015 TH367 never had a 2 week observation arc. First it was a single nighter, then the arc was 4 weeks.[2] And the coordinates of 2015 TH367 are in the constellation Aries, whereas V774104 is known to be in Pisces.--Renerpho (talk) 19:03, 14 March 2018 (UTC)[reply]
@Renerpho:, I recieved a response from David. This might get a bit complicated, but V774104 = 2015 TH367. However, the distant object at 103 AU is not V774104. I dont know what the “true” distant object ia, but it is neither V774104 nor 2015 TH367. Apparently when making a press release, Scott Sheppard accidentally referred to it as V774104. Not sure how to proceed from here, but at least that seems to be cleared up. exoplanetaryscience (talk) 21:11, 14 March 2018 (UTC)[reply]
Oh dear... @Kheider: I tag you here because you may have an idea how to proceed. This is getting complicated, indeed. At least that's the first explanation that makes sense to me. Thanks! --Renerpho (talk) 21:38, 14 March 2018 (UTC)[reply]
So, what do we have?
1. An article V774104 that should redirect to 2015 TH367, because the two are in fact the same object.
2. An article about an unnamed distant object at 103 AU that was once erroneously referred to as V774104, but is not identical with 2015 TH367. --Renerpho (talk) 21:52, 14 March 2018 (UTC)[reply]
That's pretty much it. This should get interesting. exoplanetaryscience (talk) 21:56, 14 March 2018 (UTC)[reply]
Yikes. Since 2015 TH367 ≠ the unnamed "object @ ~103 AU", then perhaps for now the two artciles should remain seperate? It might be best to keep V774104 where it is until they release more info about the "object @ ~103AU". For now all of our sources say V774104 is the object ~103 AU from the Sun. Perhaps a good footnote in the V774104 article would be useful. -- Kheider (talk) 21:59, 14 March 2018 (UTC)[reply]
If you like, I could inquire as to what the 103 AU object is supposed to be called for referential purposes. exoplanetaryscience (talk) 22:00, 14 March 2018 (UTC)[reply]
That would help. Since the "object @ ~103 AU" will likely be better known as V774104 than 2015 TH367 ever will be, I think it might be best if V774104 always re-directs to the "object @ ~103 AU", with notes explaining that press release error. -- Kheider (talk) 22:07, 14 March 2018 (UTC)[reply]
If we do that (which I don't support personally), then indicating the false designation would need to be extremely clear for minimization of confusion to someone casually reading through. exoplanetaryscience (talk) 22:11, 14 March 2018 (UTC)[reply]
It reminds me a bit of 330 Adalberta (see the story over there about its discovery). I think it would make sense to leave the V774104 as it is, and keep the two articles seperate. Since V774104 never was an official designation, this should be okay. --Renerpho (talk) 22:19, 14 March 2018 (UTC)[reply]
Bad idea here: what if after 103 AU's release, we made V774104 a disambig page to both 2015 TH367 and the intended object? exoplanetaryscience (talk) 22:29, 14 March 2018 (UTC)[reply]
Maybe after V774104 has an official designation, yes. And then add a nice paragraph to each article explaining the quirk. This will make a nice footnote in the history books. --Renerpho (talk) 22:33, 14 March 2018 (UTC)[reply]
That would work, as well as using Template:Distinguish2. Anyone Googling V774104 in the future will almost always be looking for the mystery object 103AU from the Sun. Anyone looking for 2015 TH367 will Google it by name. Either way, both articles will need to explain the quirk. -- Kheider (talk) 22:41, 14 March 2018 (UTC)[reply]
Hi - I'm curious - in 2015 you added a hatnote to this article: {{Distinguish|Longitude of the ascending node}}. I can't understand how the two have any connection at all, let alone any possiblity of confusion. Could you explain? Colonies Chris (talk) 13:52, 29 March 2018 (UTC)[reply]
I added it because some astronomers use the abbreviation “LOAN” to refer to the Longitude Of the Ascending Node. exoplanetaryscience (talk) 14:08, 29 March 2018 (UTC)[reply]
Thanks for explaining that. I've tweaked the hatnote to make that clear. Colonies Chris (talk) 10:50, 30 March 2018 (UTC)[reply]
Hi the article I have created, and have been working on, K2-155d, is currently a GA article nominee (however, I still am making edits to the article). If you don't mind, feel free helping me on the article, including improving it as well. Also, in the sections "Size and temperature" and "Orbit and host star", is there anything I can add in the article as well? --LovelyGirl7talk 03:39, 6 April 2018 (UTC)[reply]
Villiage pump
Pretty sure your comment there wound up in the wrong section. Just FYI. GMGtalk 17:55, 16 April 2018 (UTC)[reply]
Thanks for working on it as a template, and sorry I didn't get better documentation in place first. For one thing, be aware that {{Large near earth asteroid flybys 1LD}} and {{Large near earth asteroid flybys 2LD}} are templates as well. I noticed you removed the italicized diameters, which served to indicate if an asteroid had a known size, rather than just assumed. As for color, dark grey = not discovered at close approach, white = observed during close approach, light grey = close approach is after present and (obviously) not observed. exoplanetaryscience (talk) 17:48, 20 April 2018 (UTC)[reply]
I added a color code legend (colors changed). For "not discovered at close approach" I used "unobserved at close approach", because of 1942-Hermes approach in {{Large near earth asteroid flybys 5LD}} (already discovered). Yes I removed the some malformed syntax from the table (incomplete italics). The albedo range for the generically estimated sizes is still missing.Rfassbind– talk 23:49, 25 April 2018 (UTC)[reply]
Thanks! The albedo range would be 0.05-0.3, with an additional assumed H error of 0.3 (unless otherwise noted in the JPL small body database) exoplanetaryscience (talk)
There are sections on the WikiProject page dedicated to tasks (including WikiGnome tasks too), and areas on the talk page for discussing the improvement and automation of the various features of portals.
Many complaints have been lodged in the RfC to delete all portals, pointing out their various problems. They say that many portals are not maintained, or have fallen out of date, are useless, etc. Many of the !votes indicate that the editors who posted them simply don't believe in the potential of portals anymore.
It's time to change all that. Let's give them reasons to believe in portals, by revitalizing them.
The best response to a deletion nomination is to fix the page that was nominated. The further underway the effort is to improve portals by the time the RfC has run its course, the more of the reasons against portals will no longer apply. RfCs typically run 30 days. There are 19 days left in this one. Let's see how many portals we can update and improve before the RfC is closed, and beyond.
A healthy WikiProject dedicated to supporting and maintaining portals may be the strongest argument of all not to delete.
We may even surprise ourselves and exceed all expectations. Who knows what we will be able to accomplish in what may become the biggest Wikicollaboration in years.
Join our Facebook group here, and follow us on Twitter .
To opt out of future mailings about LA meetups, please remove your name from this list.
Thank you very much
The RfC discussion to eliminate portals was closed May 12, with the statement "There exists a strong consensus against deleting or even deprecating portals at this time." This was made possible because you and others came to the rescue. Thank you for speaking up.
I'd also like to let you know that the Portals WikiProject is working hard to make sure your support of portals was not in vain. Toward that end, we have been working diligently to innovate portals, while building, updating, upgrading, and maintaining them. The project has grown to 80 members so far, and has become a beehive of activity.
Our two main goals at this time are to automate portals (in terms of refreshing, rotating, and selecting content), and to develop a one-page model in order to make obsolete and eliminate most of the 150,000 subpages from the portal namespace by migrating their functions to the portal base pages, using technologies such as selective transclusion. Please feel free to join in on any of the many threads of development at the
WikiProject's talk page
, or just stop by to see how we are doing. If you have any questions about portals or portal development, that is the best place to ask them.
If you would like to keep abreast of developments on portals, keep in mind that the project's members receive updates on their talk pages. The updates are also posted here, for your convenience.
Again, we can't thank you enough for your support of portals, and we hope to make you proud of your decision. Sincerely, — The Transhumanist 10:51, 25 May 2018 (UTC)[reply]
P.S.: if you reply to this message, please {{
ping
}} me. Thank you. -TT
Disambiguation link notification for June 11
Hi. Thank you for your recent edits. An automated process has detected that when you recently edited
usually incorrect, since a disambiguation page is merely a list of unrelated topics with similar titles. (Read the FAQ • Join us at the DPL WikiProject
.)
It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 09:26, 11 June 2018 (UTC)[reply]
Near stars
When you edited the table on the List of nearest stars and brown dwarfs page, you forgot to make the bottom row spans match the changes to the top part. I would fix it but I am not so good at table formatting. :) Andrew Z. Colvin • Talk 00:10, 12 June 2018 (UTC)[reply]