Jump to content

Talk:Gamma Virginis

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Error

[edit]

users of this webpage should note that the ephemeris displayed is erroneous, being derived from the long obsolete orbital computation of Strand 1937. In reality, Gamma is just now, April 2005, appraoching apparent periastron, probably in the next few weeks (May 2005), the most spectacular binary star event of the century for northern hemisphere observers; by 2007-8 all the most interesting action will be past history! For details of the true current state of progress of this 'magnificent phenomenon'(name J.Herschel) see www.hanwellobservatory.org.uk

Christopher Taylor Hanwell Community Observatory, Oxon. , UK

15 04 05

Further to the above, please note that Christopher Taylor's observational notes on Gamma Virginis currently reside at http://www.hanwellobservatory.org.uk/astronomy/gamma-virginis.html

Naming

[edit]

i've deleted the alternative names ("arich") as the cited reference (allen) does not mention them and i have never encountered them in the astronomical literature. Macevoy (talk) 14:43, 26 May 2013 (UTC)[reply]

Leo Huckvale Hanwell Community Observatory 02 09 2010 —Preceding unsigned comment added by 87.112.215.80 (talk) 11:12, 2 September 2010 (UTC)[reply]

[edit]

Hello fellow Wikipedians,

I have just modified 2 external links on Gamma Virginis. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 16:59, 7 January 2017 (UTC)[reply]

Gamma Virginis update May 2023.

[edit]

Greetings from the Hanwell Observatory, Oxon., U.K., where gamma Vir. has been measured at least annually since 1998.38, with the exception of 2022, during which time this magnificent revolving star-system has swept through 274 degrees of its orbit, down to the latest measure on the 12.5-inch telescope here last Sunday evening of position-angle ('p.a.')= 354.1 deg. +/- 1.1, at 2023.38. For comparison, the prediction for this date from the most recent orbital ephemeris is 353.5 deg.

 A recent critical review of the whole series of Hanwell measures has demonstrated that the measured p.a.s have generally been within about 1 degree of subsequently established definitive values (which are not merely those taken from any single orbit computation), even through the 0.3-arcsecond periastron of 2005, and sometimes even closer, while never being more than 3 deg. out at worst. This should be borne in mind when looking at the tabulation of observed and predicted p.a.s given in the main article here. The ancient Strand orbit of 1937 was already wildly divergent from the true motion of this binary even before the 2005 periastron and has now long been completely irrelevant.  If the Wikipedia team would like to see a longer account of this work (450 words about), I'm happy to supply that.                        Christopher Taylor.     27.5.23 Manc0355 (talk) 08:28, 27 May 2023 (UTC)[reply]