Going to object found in Simbad does not circle target

Bug #958218 reported by Rob Burrowes
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Stellarium
Fix Released
Wishlist
Alexander Wolf

Bug Description

Search for lowers, and it will find Lower's Nebula in Simbad. Going to this target works, but there is no marker on the display to show the nebula location. Only objects found locally get the target circled.

There is also no location/object information shown in the top right, nor does the telescope goto work for these targets.

Tags: search

Related branches

Revision history for this message
Rob Burrowes (rob-burrowes) wrote :

Top left, not top right

Revision history for this message
Rob Burrowes (rob-burrowes) wrote :

2012-03-18T13:29:52
Mac OS X 10.5
Compiled with GCC 4.0.1
Qt runtime version: 4.7.3
Qt compilation version: 4.7.3
Addressing mode: 32-bit
Model Name: Mac mini
Model Identifier: Macmini1,1
Processor Name: Intel Core Solo
Processor Speed: 1.5 GHz
Number Of Processors: 1
Memory: 2 GB
Chipset Model: GMA 950
VRAM (Total): 64 MB of Shared System Memory
VRAM (Total): 64 MB of Shared System Memory
/Applications/Stellarium.app/Contents/MacOS/stellarium
 -------------------------------------------------------
[ This is Stellarium 0.11.2 - http://www.stellarium.org ]
[ Copyright (C) 2000-2012 Fabien Chereau et al ]

Changed in stellarium:
status: New → Confirmed
milestone: none → 0.11.3
Revision history for this message
Khalid AlAjaji (kajaji) wrote :

The result of SIMBD search is only a pair of coordinates, so Stellarium can only move its view to that coordinates.

See Bogdan's answer to a similar question here: Question #113120

https://answers.launchpad.net/stellarium/+question/113120

Revision history for this message
Rob Burrowes (rob-burrowes) wrote : Re: [Bug 958218] Re: Going to object found in Simbad does not circle target

Could it still put the target circle at those coordinates?

You do know the name (from the search field) and the coordinates, so the
text could reflect just these facts (possibly by creating a temporary
entry in memory for the target).

On 19/03/12 3:50 PM, Khalid AlAjaji wrote:
> The result of SIMBD search is only a pair of coordinates, so Stellarium
> can only move its view to that coordinates.
>
> See Bogdan's answer to a similar question here: Question #113120
>
> https://answers.launchpad.net/stellarium/+question/113120
>

--
--
Rob Burrowes Ph: +64 9 923 2308 (Internal 82308)
Research Data Services Cell: +64 27 4731856 (internal 64209)
Technical Lead
Centre for eResearch
The University of Auckland
Private Bag 92019 http://www.sit.auckland.ac.nz/~rob
Auckland Mail Centre http://www.burrowes.org/
Auckland 1142 http://www.wikarekare.org/
NEW ZEALAND

Meatball_py (renws1990)
Changed in stellarium:
assignee: nobody → Wenshan Ren (renws1990)
Revision history for this message
Bogdan Marinov (daggerstab) wrote :

As it is actually a requested feature, I'm setting it as a Wishlist item.

Any ideas who is "Wenshan Ren" and why they assigned the bug to themselves?

Changed in stellarium:
importance: Undecided → Wishlist
Revision history for this message
Bogdan Marinov (daggerstab) wrote :

There are actually two issues here: the handling of objects that don't exist in Stellarium's databases at all, and the handling of objects that are in Stellarium, but under another name. I think that the second case may be easier to deal with.

Revision history for this message
Rob Burrowes (rob-burrowes) wrote :

On 20/03/12 8:25 AM, Bogdan Marinov wrote:
> As it is actually a requested feature, I'm setting it as a Wishlist
> item.
>
> Any ideas who is "Wenshan Ren" and why they assigned the bug to
> themselves?
>
> ** Changed in: stellarium
> Importance: Undecided => Wishlist
>
No, no idea who Wenshan is.

--
--
Rob Burrowes Ph: +64 9 923 2308 (Internal 82308)
Research Data Services Cell: +64 27 4731856 (internal 64209)
Technical Lead
Centre for eResearch
The University of Auckland
Private Bag 92019 http://www.sit.auckland.ac.nz/~rob
Auckland Mail Centre http://www.burrowes.org/
Auckland 1142 http://www.wikarekare.org/
NEW ZEALAND

Revision history for this message
Meatball_py (renws1990) wrote :

Hi Bogdan and Rob,

I'm Wenshan, intending to participate in GSoC 2012.
I want to get myself started by fixing some bugs. Alex told me I need
to assign a
bug to myself firstly, so I did it.

Do I need to unassign it?

Best Regards,
Wenshan

On Tue, Mar 20, 2012 at 6:25 AM, Bogdan Marinov <email address hidden> wrote:
> As it is actually a requested feature, I'm setting it as a Wishlist
> item.
>
> Any ideas who is "Wenshan Ren" and why they assigned the bug to
> themselves?
>
> ** Changed in: stellarium
>   Importance: Undecided => Wishlist
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/958218
>
> Title:
>  Going to object found in Simbad does not circle target
>
> Status in Stellarium:
>  Confirmed
>
> Bug description:
>  Search for lowers, and it will find Lower's Nebula in Simbad. Going to
>  this target works, but there is no marker on the display to show the
>  nebula location.  Only objects found locally get the target circled.
>
>  There is also no location/object information shown in the top right,
>  nor does the telescope goto work for these targets.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/stellarium/+bug/958218/+subscriptions

--
Happy Hacking,

Wenshan Ren
<email address hidden>

Revision history for this message
treaves (treaves) wrote :

Please, if you fee you can resolve it, we'd love the help!

Thanks Wenshan.

On Mon, Mar 19, 2012 at 5:30 PM, Wenshan Ren <email address hidden> wrote:

> Hi Bogdan and Rob,
>
> I'm Wenshan, intending to participate in GSoC 2012.
> I want to get myself started by fixing some bugs. Alex told me I need
> to assign a
> bug to myself firstly, so I did it.
>
> Do I need to unassign it?
>
>
> Best Regards,
> Wenshan
>
> On Tue, Mar 20, 2012 at 6:25 AM, Bogdan Marinov <email address hidden>
> wrote:
> > As it is actually a requested feature, I'm setting it as a Wishlist
> > item.
> >
> > Any ideas who is "Wenshan Ren" and why they assigned the bug to
> > themselves?
> >
> > ** Changed in: stellarium
> > Importance: Undecided => Wishlist
> >
> > --
> > You received this bug notification because you are a bug assignee.
> > https://bugs.launchpad.net/bugs/958218
> >
> > Title:
> > Going to object found in Simbad does not circle target
> >
> > Status in Stellarium:
> > Confirmed
> >
> > Bug description:
> > Search for lowers, and it will find Lower's Nebula in Simbad. Going to
> > this target works, but there is no marker on the display to show the
> > nebula location. Only objects found locally get the target circled.
> >
> > There is also no location/object information shown in the top right,
> > nor does the telescope goto work for these targets.
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/stellarium/+bug/958218/+subscriptions
>
>
> --
> Happy Hacking,
>
> Wenshan Ren
> <email address hidden>
>
> --
> You received this bug notification because you are subscribed to
> Stellarium.
> https://bugs.launchpad.net/bugs/958218
>
> Title:
> Going to object found in Simbad does not circle target
>
> Status in Stellarium:
> Confirmed
>
> Bug description:
> Search for lowers, and it will find Lower's Nebula in Simbad. Going to
> this target works, but there is no marker on the display to show the
> nebula location. Only objects found locally get the target circled.
>
> There is also no location/object information shown in the top right,
> nor does the telescope goto work for these targets.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/stellarium/+bug/958218/+subscriptions
>

Changed in stellarium:
milestone: 0.11.3 → none
Changed in stellarium:
assignee: Meatball_py (renws1990) → nobody
Revision history for this message
Alexander Wolf (alexwolf) wrote :

I think create a temporary object with coordinates from SIMBAD is good idea for solving this issue.

Revision history for this message
Bogdan Marinov (daggerstab) wrote :

As I pointed out in comment #6, this is actually two issues with different solutions.

"Selecting" existing objects can be done by asking SIMBAD for their identifiers (HIP or NGC number) and finding the appropriate object in Stellarium.

As for creating temporary objects for objects that are not in Stellarium's catalogs... I don't think it's a good idea for a number of reasons. (Last but not least, I doubt the ability of the currently active developers to implement it without creating more problems than those that are solved.)

Revision history for this message
Pierluigi Panunzi (piellepi) wrote :

Hi!
I can confirm an issue about finding stars

I have downloaded all the 9 star catalogs and I tried searching some stars.

Searching "Gliese1" , the star HD 225213 was found (by means of SIMBAD lookup), but trying to center the map on it (pressing Enter) , the star doesn't appear at all. It's a 8.55 magnitude M2V star...

Searching instead "HD 225213", the program finds it and going to it with Enter, now the star is visible, named as
HIP 439, SAO 192348 and HD 225213... (but no Gliese1 alias...)

Pierluigi

Changed in stellarium:
status: Confirmed → In Progress
Changed in stellarium:
milestone: none → 1.0.0
status: In Progress → Fix Committed
status: Fix Committed → In Progress
assignee: nobody → Alexander Wolf (alexwolf)
Revision history for this message
Alexander Wolf (alexwolf) wrote :

Behaviour of Search Tool has been changed:
a) It uses results from SIMBAD for search among Stellarium's objects
b) It blocks position when coordinates are used (both data SIMBAD, and a manual pointing to the coordinates) - it's not a marker for SIMBAD data, but it's more useful now.

Changed in stellarium:
status: In Progress → Fix Committed
status: Fix Committed → In Progress
tags: added: search
Changed in stellarium:
status: In Progress → Fix Committed
Revision history for this message
Alexander Wolf (alexwolf) wrote :

Please check version 0.90.0.8715 - I've changed behaviour of Search Tool.

Changed in stellarium:
milestone: 1.0.0 → 0.15.1
no longer affects: stellarium/0.15
Changed in stellarium:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.