New star catalog with Gaia DR3

CMakeLists.txt

@@ -541,7 +541,7 @@ ADD_PLUGIN(Calendars 1)
 ADD_PLUGIN(Exoplanets 1)
 ADD_PLUGIN(EquationOfTime 1)
 ADD_PLUGIN(MeteorShowers 1)
-ADD_PLUGIN(MissingStars 1)
+ADD_PLUGIN(MissingStars 0)
 ADD_PLUGIN(NavStars 1)
 ADD_PLUGIN(Novae 1)
 ADD_PLUGIN(Observability 1)

guide/app_accuracy.tex

@@ -48,38 +48,32 @@ \chapter{Accuracy}
 \section{Date Range}
 \label{sec:Accuracy:DateRange}
 
-The calendar dates are limited to a very wide interval of years, -100.000\ldots100.000. 
+The calendar dates are limited to a very wide interval of years, $-100,000\ldots100,000$. 
 This is mostly useful to visualize the effect of stellar proper motions or the wobbling 
 motion of Earth's axis known as precession. 
 If you observe the other planets, this is way beyond what current models are able to show! 
 Observe for example the Moon: you will find that it seems to run 
 on a polar orbit around +78.000 and even retrograde on a highly elongated orbit a few millennia after that. 
 This is obvious nonsense, caused by extrapolating mathematical models in inappropriate ways. 
 
-\section{Stellar Proper Motion}
-\label{sec:Accuracy:ProperMotion}
-
-Even though you can follow stellar proper motion for tens of thousands of years, 
-please note that the computation only takes the linear components $\Delta\alpha$, $\Delta\delta$ into account. 
-For times far from today, a true 3D computation would be required, 
-so that also changes in distance (and thus, brightness) could be simulated. 
-Still, the simulation here should give a good impression which close and/or fast stars 
-will move over time, and thus how constellations become deformed.
-
-Note that due to the way the stars are stored in catalogs, zooming in on fast stars like Arcturus 
-may even cease to display such stars when their original area in the sky is no longer in view.
-
-Also, binary stars seem to break apart because Stellarium does not store them as systems 
-revolving about their combined center of gravity.
-
-These known deficits were also identified in a recent study
-\citep{deLorenzis:2018}, which emphasized errors with Arcturus, Dubhe,
-Sirius, Toliman and Vega which already deviate noticeably from their
-correct locations around 2500BC.  If you need accurate stellar
-positions for earlier prehistory from a free and open-source program,
-it seems only \program{Cartes du Ciel} currently can be recommended as
-on a par with the best available solutions.
-
+\section{Stellar Astrometry}
+\label{sec:Accuracy:Astrometry}
+
+Even though you can follow movements of stars on the sky for tens of thousands of years, 
+please note that the precision of these predictions are limited by the precision of the data we have at 
+the present time provided by Hipparcos for bright stars and Gaia. Most of the stars brighter than magnitude 10.5 
+have 3D position and 3D velocity data (i.e., 6D astrometry) in our star catalogs, thus their 6D astrometry are computed 
+at any epoch by assuming linear motion with constant velocity. These calculation provides arcseconds level accuracy
+of stellar position, arcseconds per year level accuracy of proper motions, arcseconds level accuracy of parallax and km/s 
+level accuracy of radial velocity in the previous and next tens of thousands of years. For stars fainter than magnitude 10.5 but brighter
+than magnitude 16.75, 2D computation is performed such that RA/DEC positions are computed from RA/DEC proper motions separately and assume
+constant proper motion. For stars fainter than magnitude 16.75, no astrometry propagation is performed hence their RA/DEC stay constant at any epoch.
+
+In the study of \citep{deLorenzis:2018}, which emphasized sky position errors with bright high proper motions star like Arcturus, 
+Dubhe, Sirius, Toliman and Vega which deviate noticeably from their correct locations even at around 2500BC with Stellarium 
+0.17.0 released on 21 Dec 2017. The star catalogs and astrometry propagation algorithms have been significantly improved in 
+December 2024, which has solved the problem outlined in the study. But binary stars seem to break apart because Stellarium does 
+not store them as systems revolving about their combined center of gravity.
 
 \section{Planetary Positions}
 \label{sec:Accuracy:Planets}

guide/guide.bib

@@ -2181,3 +2181,29 @@ @article{Adler:2002
        month = sep,
        pages = {94-98}
 }
+
+@BOOK{2012asas.book.....V,
+       author = {{van Altena}, William F.},
+        title = "{Astrometry for Astrophysics}",
+         year = 2012,
+       adsurl = {https://ui.adsabs.harvard.edu/abs/2012asas.book.....V},
+      adsnote = {Provided by the SAO/NASA Astrophysics Data System}
+}
+
+@ARTICLE{2016A&A...595A...1G,
+       author = {{Gaia Collaboration} and et al.},
+        title = "{The Gaia mission}",
+      journal = {Astronomy \& Astrophysics},
+     keywords = {space vehicles: instruments, Galaxy: structure, astrometry, parallaxes, proper motions, telescopes, Astrophysics - Instrumentation and Methods for Astrophysics},
+         year = 2016,
+        month = nov,
+       volume = {595},
+          eid = {A1},
+        pages = {A1},
+          doi = {10.1051/0004-6361/201629272},
+archivePrefix = {arXiv},
+       eprint = {1609.04153},
+ primaryClass = {astro-ph.IM},
+       adsurl = {https://ui.adsabs.harvard.edu/abs/2016A&A...595A...1G},
+      adsnote = {Provided by the SAO/NASA Astrophysics Data System}
+}

plugins/RemoteControl/src/SimbadService.cpp

@@ -66,7 +66,7 @@ class SimbadLookupTask :public QRunnable
 
 		loop.exec();
 		//at this point, the reply is finished
-		//and we can extract information using getReply
+		//and we can extract information using getResults
 		status = reply->getCurrentStatus();
 		statusString = reply->getCurrentStatusString();
 		errorString = reply->getErrorString();

plugins/Satellites/src/Satellite.cpp

@@ -344,9 +344,10 @@ QString Satellite::getInfoString(const StelCore *core, const InfoStringGroup& fl
 	{
 		const int decimals = 2;
 		const float airmass = getAirmass(core);
-		oss << QString("%1: <b>%2</b>").arg(q_("Approx. magnitude"), QString::number(getVMagnitude(core), 'f', decimals));
+		const float mag=getVMagnitude(core);
+		oss << QString("%1: <b>%2</b>").arg(q_("Approx. magnitude"), QString::number(mag, 'f', decimals));
 		if (airmass>-1.f) // Don't show extincted magnitude much below horizon where model is meaningless.
-			oss << QString(" (%1 <b>%2</b> %3 <b>%4</b> %5)").arg(q_("reduced to"), QString::number(getVMagnitudeWithExtinction(core), 'f', decimals), q_("by"), QString::number(airmass, 'f', decimals), q_("Airmasses"));
+			oss << QString(" (%1 <b>%2</b> %3 <b>%4</b> %5)").arg(q_("reduced to"), QString::number(getVMagnitudeWithExtinction(core, mag), 'f', decimals), q_("by"), QString::number(airmass, 'f', decimals), q_("Airmasses"));
 		oss << "<br />";
 	}
 

plugins/Supernovae/src/Supernova.cpp

@@ -114,14 +114,14 @@ QString Supernova::getMaxBrightnessDate(const StelCore *core, const double JD) c
 	return StelApp::getInstance().getLocaleMgr().getPrintableDateLocal(JD, core->getUTCOffset(JD));
 }
 
-QString Supernova::getMagnitudeInfoString(const StelCore *core, const InfoStringGroup& flags, const int decimals) const
+QString Supernova::getMagnitudeInfoString(const StelCore *core, const InfoStringGroup& flags, const int decimals, const float& magOffset) const
 {
 	const float maglimit = 21.f;
 	QString res;
 
 	if (flags&Magnitude)
 	{
-		if (getVMagnitude(core) <= maglimit)
+		if (getVMagnitude(core) + magOffset <= maglimit)
 			res = StelObject::getMagnitudeInfoString(core, flags, decimals);
 		else
 		{

plugins/Supernovae/src/Supernova.hpp

@@ -96,7 +96,7 @@ class Supernova : public StelObject
 	QString getEnglishName(void) const override;
 
 protected:
-	QString getMagnitudeInfoString(const StelCore *core, const InfoStringGroup& flags, const int decimals=1) const override;
+	QString getMagnitudeInfoString(const StelCore *core, const InfoStringGroup& flags, const int decimals=1, const float& magOffset=0.f) const override;
 
 private:
 	bool initialized;

src/CMakeLists.txt

@@ -130,6 +130,8 @@ SET(stellarium_lib_SRCS
      core/StelOpenGLArray.cpp
      core/StelHips.hpp
      core/StelHips.cpp
+     core/StelHealpix.hpp
+     core/StelHealpix.cpp
      core/TextureAverageComputer.hpp
      core/TextureAverageComputer.cpp
 
@@ -829,6 +831,16 @@ IF(ENABLE_TESTING)
     ADD_TEST(testAirmass testAirmass)
     SET_TARGET_PROPERTIES(testAirmass PROPERTIES FOLDER "src/tests")
 
+    SET(tests_testAstrometry_SRCS
+        tests/testAstrometry.hpp
+        tests/testAstrometry.cpp
+    )
+    ADD_EXECUTABLE(testAstrometry ${tests_testAstrometry_SRCS})
+    TARGET_LINK_LIBRARIES(testAstrometry ${TESTS_LIBRARIES})
+    ADD_DEPENDENCIES(buildTests testAstrometry)
+    ADD_TEST(testAstrometry testAstrometry)
+    SET_TARGET_PROPERTIES(testAstrometry PROPERTIES FOLDER "src/tests")
+
     SET(tests_testGeomMath_SRCS
         tests/testGeomMath.hpp
         tests/testGeomMath.cpp

src/core/SimbadSearcher.cpp

@@ -194,7 +194,7 @@ SimbadLookupReply* SimbadSearcher::lookup(const QString& serverUrl, const QStrin
 {
 	// Create the Simbad query
 	QString url(serverUrl);
-	QString query = "format object \"%COO(d;A D)\\n%IDLIST(HIP)\\n%IDLIST(1)\"\n";
+	QString query = "format object \"%COO(d;A D)\\n%IDLIST(HIP)\\n%IDLIST(Gaia DR3)\\n%IDLIST(1)\"\n";
 	query += QString("set epoch J2000\nset limit %1\n query id ").arg(maxNbResult);
 	query += objectName;
 	QByteArray ba = QUrl::toPercentEncoding(query, "", "");

src/core/StelGeodesicGrid.hpp

@@ -52,7 +52,7 @@ class StelGeodesicGrid
 
 	int getMaxLevel(void) const {return maxLevel;}
 
-	static int nrOfZones(int level) {return (20<<(level<<1));} // 20*4^level
+	static int nrOfZones(int level) {return ((20<<(level<<1)) + 1);} // 20*4^level local zones
 
 	int getNrOfZones(void) const {return nrOfZones(maxLevel);}