Project

General

Profile

Support #5117

Removal of HOST_GALAXY

Added by Chris D'Andrea almost 6 years ago. Updated almost 6 years ago.

Status:
New
Priority:
High
Assignee:
Start date:
12/20/2013
Due date:
% Done:

0%

Estimated time:
Duration:

Description

Is there a way of removing the host galaxy link without simply overwriting a new one? I've rejigged the host-galaxy matching via the method Ravi used for the SDSS Data Release. In most cases the host is the same, but there are a fair number where the host is different, and in some the object is now considered 'hostless'. So I'd like to be able to REMOVE the host galaxy link, and then re-post on those where there is a new host galaxy ID. Since the link is created via a post, I'm not sure if this is possible; there is probably some error checking that makes sure a new post points to a target, so I probably can't make a post with an empty ID field ...

I'd like to get this done ASAP so I can use these galaxy IDs for the final AAT run.

History

#1 Updated by Rollin Thomas almost 6 years ago

This is possible for tags but not for other attachments. Being able to do something like this for host_galaxy makes sense. I wonder: should we actually delete the host galaxy value or should it actually be something more informative like "hostless" (as opposed to undefined)?

#2 Updated by Chris D'Andrea almost 6 years ago

I wouldn't be adverse to that. The only issue is that currently I ingest the target BEFORE i run any hostmatching; I then update the transient page with the host galaxy information from inside the hostmatch code. If the host_galaxy is required to be filled, then everything will either be 'hostless' on creation, or I will have to ingest the SN target from within the HOSTMATCH code, which doesn't make much sense. Both are possible, of course, just less elegant.

But in general, yes, if I can update those targets with a 'hostless' value, that would be great.

#3 Updated by Rollin Thomas almost 6 years ago

Chris D'Andrea wrote:

I wouldn't be adverse to that. The only issue is that currently I ingest the target BEFORE i run any hostmatching; I then update the transient page with the host galaxy information from inside the hostmatch code. If the host_galaxy is required to be filled, then everything will either be 'hostless' on creation, or I will have to ingest the SN target from within the HOSTMATCH code, which doesn't make much sense. Both are possible, of course, just less elegant.

But in general, yes, if I can update those targets with a 'hostless' value, that would be great.

Think of it this way. If there is nothing set, it means we don't have a host galaxy association. If we set it to hostless, we have a host galaxy association of hostless. That is, hostless is like a special "null" host that actually means "no host" instead of "we haven't set the host galaxy yet" which is what we have when you first ingest a target.

#4 Updated by Chris D'Andrea almost 6 years ago

Okay, that would be good: no association, or a special null value that is hostless.

Let me know when/how I can update certain targets to hostless!



Also available in: Atom PDF