Re: [Celestia-developers] Adding Globulars to qt4 DSO Browser
Real-time 3D visualization of space
Status: Beta
Brought to you by:
cjlaurel
From: Steve P. <car...@ya...> - 2008-11-16 14:39:44
|
Has anyone ever come up with how to include QT4 as a 3rdParty lib. How many are needed, how big that would be, and so on and son. The 4 QT4 libs used by ISIS are 120+ mb. This could get to be a pretty big download if it part of Celestia. Steve. --- On Sun, 11/16/08, Fridger Schrempp <fri...@de...> wrote: From: Fridger Schrempp <fri...@de...> Subject: Re: [Celestia-developers] Adding Globulars to qt4 DSO Browser To: "vincent" <vin...@fr...> Cc: cel...@li... Date: Sunday, November 16, 2008, 7:47 AM Vincent, vincent wrote: > Fridger Schrempp wrote: > >> In my latest build of celestia-qt4, I had a look at your recent changes in the >> celestial browser. For now this looks nice. > > Good! :-) > Did you have a look at the issue I reported in my previous post? Yes. While for galaxies the Hubble types provide morphological info in form of a finite number of short strings like "Sa", "SBa", "E0", ..., for the globulars one would have to use a modified getType() method, which is no problem, of course. At this early stage of my globular code, I did not want to do this, until we have agreed about how to characterize globulars morphologically. As I mentioned, there are no well-known accronyms and the names of the two relevant King parameters are pretty long words... So it's really best to leave things for now as in your code. We just should not forget about getting back to a more general discussion about these issues after 1.6.0 I would say. > > Is there a way to make a distinction between visual and spectroscopic binaries, > apart from the fact that they're loaded from different catalog files? If so, > thanks for enlightening me. I did not implement a respective flag into my data sets, because of this longstanding "interference" with Grant's nearstars.stc database. The latter does NOT distinguish at all, not even between multiple and single stars. Hence, without modifying things appropriately, all you could do at present is ONE entry in the celestial browser: /multiple stars/ with visualbins, spectbins and the multiple stars from nearstars all filled in. It should be easy to separate off multiple stars from Grant's nearstars listing. As I stated MANY times in the past, I would have ordered Celestia's multiple stars differently, i.e. mainly according to distinction criteria based on /physics/... Fridger > > >> vincent wrote: >>> Actually, the qt4 code is not responsible for the fact that the 'Type' column >>> displays the Hubble Type for galaxies and the DSO type for other DSOs. This >>> issue comes from the dso code itself, and more precisely from the getType() method: >>> >>> In opencluster.cpp: >>> const char* OpenCluster::getType() const >>> { >>> return "Open cluster"; >>> } >>> >>> In nebula.cpp: >>> const char* Nebula::getType() const >>> { >>> return "Nebula"; >>> } >>> >>> In globular.cpp: >>> const char* Globular::getType() const >>> { >>> return "Globular"; >>> } >>> >>> In galaxy.cpp: >>> const char* Galaxy::getType() const >>> { >>> return GalaxyTypeNames[(int) type].name; >>> } >>> >>> ------------------------------------------------------------------ >>> Shouldn't we just make Galaxy::getType return "Galaxy", and add a >>> Galaxy::getHubbleType() method? >>> ------------------------------------------------------------------ >>> >>> @+ >>> Vincent >>> >>> >>> Selon Fridger Schrempp <fri...@de...>: >>> >>>> vincent wrote: >>>>> Fridger, >>>>> >>>>> We agree that the listing of datas in the DSO browser does need some more discussion. >>>>> Since this doesn't only apply to Globulars, but to all DSOs, would you agree on first >>>>> adding Globulars to the DSO browser without making any other change to the display of >>>>> datas? This to keep the qt4 version in sync with other versions. At least, we can make >>>>> one single change to prevent the main DSO type to be displayed in the 'Type' column for >>>>> DSOs other than galaxies. Once this is done, we will have time to discuss about the list >>>>> of datas which should be listed for each DSO type. This way, this discussion could be >>>>> even delayed to after the release of 1.6. >>>> It's certainly better to have the globulars included in the DSO browser than >>>> not having them. So, it's fine with me, but all this REALLY deserves >>>> improvement... >>>> >>>> Fridger >>>> >>>>> @+ >>>>> Vincent >>>>> >>>>> >>>>> >>>>> Selon Fridger Schrempp <fri...@de...>: >>>>> >>>>>> vincent wrote: >>>>>>> Fridger Schrempp wrote: >>>>>>> >>>>>>>> Vincent, >>>>>>>> >>>>>>>> what did you put in as "Type" for the globulars? >>>>>>> Fridger, >>>>>>> >>>>>>> I was just about to ask you what should be listed in the 'Type' column >>>>>>> for Globulars. I personnaly didn't put anything. So far, the 'main' >>>>>>> DSO type is listed for DSOs other than galaxies, i.e., 'Open cluster' and >>>>>>> 'Nebula'. So it will return "Globular" for globulars at each line >>>>>>> if no change is made to the current code, what is of course unsatisfying. >>>>>>> What do you reckon ? Should be hide the 'Type' column for DSOs other than >>>>>>> galaxies? >>>>>> The "type" is supposed to be a /morphological/ class type specification, like >>>>>> the the Hubble classes for galaxies. While for globulars, there are such >>>>>> classes, too, they are little known, quite unlike the corresponding King model >>>>>> parameters = CoreRadius & King Concentration! The latter completely >>>>>> characterize the globular morphology. That's why I displayed these on the >>>>>> canvas at the location of the Hubble type for galaxies. Unfortunately, these >>>>>> words are LONG and I don't know of any sensible abbreviations/accronyms. >>>>>> >>>>>>>> Altogether, I think for DSO's also a suitable "size" information should be >>>>>>>> displayed. >>>>>>> I'll mind it. As for Globulars, should the core radius and King concentration >>>>>>> values be listed as well? >>>>>> I am not sure I understand your "I'll mind it"? >>>>>> >>>>>> The listing of DSO data in the browser, should really be discussed in more >>>>>> detail. Like 'AppMag' and 'distance' tacitly refer to a particular location of >>>>>> the observer. Is it assumed that he/she is on Earth, or do the values change >>>>>> depending on the observer's position? >>>>>> >>>>>> Similarly, a "size" information may be location dependent. >>>>>> >>>>>> For astronomers, the subtended angular size as seen from Earth is a useful >>>>>> quantity, but it is again location dependent. I am also not happy to quote DSO >>>>>> distances in light years throughout. This is VERY unusual for professionals! >>>>>> >>>>>> We could list some absolute (photometric) radius definition for ALL DSO's. The >>>>>> most useful universal one is the mu25 isophote radius that is given in most >>>>>> catalogs. We explicitly have r_mu25 for globulars in our Celestia database. >>>>>> >>>>>> Galaxies need more than one size parameter, unless one focusses on the largest >>>>>> one in some sense. >>>>>> >>>>>> Fridger >>>>>>> @+ >>>>>>> Vincent >>>>>>> >>>>>>> >>>>>>>> vincent wrote: >>>>>>>>> The following change adds Globulars to the qt4 DSO Browser: >>>>>>>>> http://vincent.giangiulio.perso.sfr.fr/celestia/dev/qtdsobrowserpatch.zip >>>>>>>>> >>>>>>>>> It also adds: >>>>>>>>> - A marker size combobox >>>>>>>>> - Arrows to the marker symbol combobox >>>>>>>>> >>>>>>>>>> screenshot: >>>>>>>>> http://vincent.giangiulio.perso.sfr.fr/celestia/dev/qtdsobrowser2.jpg >>>>>>>>> >>>>>>>>> If the addition of the marker size option is OK to you, I'll make the >>>>>>>>> change to the star browser as well. >>>>>>>>> >>>>>>>>> @+ >>>>>>>>> Vincent ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Celestia-developers mailing list Cel...@li... https://lists.sourceforge.net/lists/listinfo/celestia-developers |