I'm wondering about how to submit what I guess amounts to data
corrections to VSX. Reading through the guidelines, they seem to focus
on submission of a new variable star and what/how to include supporting
data.

In looking through VSX and some of the reference information cited in
an entry, I've found a nested inaccuracy in the Study ref. data entry.
It's probably a just a small detail (and maybe I'm reading it wrong)
but I know you want the database to be as accurate as possible.  I'll
save the details for actual submission, but I'm not too clear on how to
go about this.

Thanks for your help!

Rick De Graeve
AAVSO - DGR

Hi Rick,

To tell you the truth, I'd rather you didn't save the details for
actual submission.  Please give me an example of what you're talking
about.  If this is a systemic problem, I'll want to find a back-end
solution to it, rather than relying on user submissions of corrected
data.  If it's something very localized, then user submissions may be
OK.  But I'd like to make that decision first.  So please show me what
you've got.  Thanks!

Christopher Watson
Principal Architect
VSX

On 5/2/07, rcdegraeve <rcdegraeve@...> wrote:
> I'm wondering about how to submit what I guess amounts to data
> corrections to VSX. Reading through the guidelines, they seem to focus
> on submission of a new variable star and what/how to include supporting
> data.
>
> In looking through VSX and some of the reference information cited in
> an entry, I've found a nested inaccuracy in the Study ref. data entry.
> It's probably a just a small detail (and maybe I'm reading it wrong)
> but I know you want the database to be as accurate as possible.  I'll
> save the details for actual submission, but I'm not too clear on how to
> go about this.
>
> Thanks for your help!
>
> Rick De Graeve
> AAVSO - DGR
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>

Hello Chris,

I apologize for not including the info in my original post but I
wasn't sure it would be okay.

Anyway...

My interest is mostly an Miras and SRs. Looking into some SRs in
Cephus I came across an what may be inaccurate info in VSX for AN CEP
(haven't had time to look into any more). The "Study ref." in the
database notes "C.Payne-Gaposchkin HA 118, N27, 1952."  Now, this
information as text only is correct as far as it goes (since it
doesn't reference the field). The problem seems to be where it
points. When following the hot spot, it takes you to the abstract for
Milton Field 27, which covers stars in Hydra, Leo and Sextans.
Digging a little deeper in the Harvard Annals, I found that, though
AN CEP is, indeed,  in vol 118, No. 27, it is in the abstract for
Milton Field 1, not 27. I'm guessing it could be a misinterpertation
of the "N27".

It could be possible that I'm misinterperting what I see but I
thought I'd bring it up the the discussion group. I hope this doesn't
send anyone off on any wild goose chases!

Rick De Graeve


--- In vsx-dis@yahoogroups.com, "Christopher Watson" <skygeex@...>
wrote:
>
> Hi Rick,
>
> To tell you the truth, I'd rather you didn't save the details for
> actual submission.  Please give me an example of what you're talking
> about.  If this is a systemic problem, I'll want to find a back-end
> solution to it, rather than relying on user submissions of corrected
> data.  If it's something very localized, then user submissions may
be
> OK.  But I'd like to make that decision first.  So please show me
what
> you've got.  Thanks!
>
> Christopher Watson
> Principal Architect
> VSX
>
> On 5/2/07, rcdegraeve <rcdegraeve@...> wrote:
> > I'm wondering about how to submit what I guess amounts to data
> > corrections to VSX. Reading through the guidelines, they seem to
focus
> > on submission of a new variable star and what/how to include
supporting
> > data.
> >
> > In looking through VSX and some of the reference information
cited in
> > an entry, I've found a nested inaccuracy in the Study ref. data
entry.
> > It's probably a just a small detail (and maybe I'm reading it
wrong)
> > but I know you want the database to be as accurate as possible.
I'll
> > save the details for actual submission, but I'm not too clear on
how to
> > go about this.
> >
> > Thanks for your help!
> >
> > Rick De Graeve
> > AAVSO - DGR
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>

Just a note on the consistency of the error... I just took a quick
look at RW CEP and find the same type of mis-direction at least for 2
of these that the Study ref. points to the Harvard Annals. This one
also points to Milton Field 27 abstract and it should point to Milton
Field 9.

... hope this is doing some good.

Rick

--- In vsx-dis@yahoogroups.com, "rcdegraeve" <rcdegraeve@...> wrote:
>
> Hello Chris,
>
> I apologize for not including the info in my original post but I
> wasn't sure it would be okay.
>
> Anyway...
>
> My interest is mostly an Miras and SRs. Looking into some SRs in
> Cephus I came across an what may be inaccurate info in VSX for AN
CEP
> (haven't had time to look into any more). The "Study ref." in the
> database notes "C.Payne-Gaposchkin HA 118, N27, 1952."  Now, this
> information as text only is correct as far as it goes (since it
> doesn't reference the field). The problem seems to be where it
> points. When following the hot spot, it takes you to the abstract
for
> Milton Field 27, which covers stars in Hydra, Leo and Sextans.
> Digging a little deeper in the Harvard Annals, I found that, though
> AN CEP is, indeed,  in vol 118, No. 27, it is in the abstract for
> Milton Field 1, not 27. I'm guessing it could be a
misinterpertation
> of the "N27".
>
> It could be possible that I'm misinterperting what I see but I
> thought I'd bring it up the the discussion group. I hope this
doesn't
> send anyone off on any wild goose chases!
>
> Rick De Graeve
>
>
> --- In vsx-dis@yahoogroups.com, "Christopher Watson" <skygeex@>
> wrote:
> >
> > Hi Rick,
> >
> > To tell you the truth, I'd rather you didn't save the details for
> > actual submission.  Please give me an example of what you're
talking
> > about.  If this is a systemic problem, I'll want to find a back-
end
> > solution to it, rather than relying on user submissions of
corrected
> > data.  If it's something very localized, then user submissions
may
> be
> > OK.  But I'd like to make that decision first.  So please show me
> what
> > you've got.  Thanks!
> >
> > Christopher Watson
> > Principal Architect
> > VSX
> >
> > On 5/2/07, rcdegraeve <rcdegraeve@> wrote:
> > > I'm wondering about how to submit what I guess amounts to data
> > > corrections to VSX. Reading through the guidelines, they seem
to
> focus
> > > on submission of a new variable star and what/how to include
> supporting
> > > data.
> > >
> > > In looking through VSX and some of the reference information
> cited in
> > > an entry, I've found a nested inaccuracy in the Study ref. data
> entry.
> > > It's probably a just a small detail (and maybe I'm reading it
> wrong)
> > > but I know you want the database to be as accurate as
possible.
> I'll
> > > save the details for actual submission, but I'm not too clear
on
> how to
> > > go about this.
> > >
> > > Thanks for your help!
> > >
> > > Rick De Graeve
> > > AAVSO - DGR
> > >
> > >
> > >
> > >
> > >
> > > Yahoo! Groups Links
> > >
> > >
> > >
> > >
> >
>

Subject: [vsx-dis] Re: How to note a possible correction to VSX data


Hi, Rick,

The problem here lies in the catalogue source.
What I mean is, up to last year, when people started submitting new
variables to the database, VSX was only a colection of catalogues imported
as they are.  This means that if the original catalogue has errors, the
errors will be in the DB and it is our goal to correct them when we find
them. People like you noting these mistakes and submitting a revision to
correct them is what we really need.
Once the catalogue imports were ended, we knew (from the beginning) that a
neverending task was ahead of us: correcting all the mistakes and updating
all the data included in VSX.
We also have stars with more than one entry due to the nature of the
database: if the star is in several catalogues, all those entries will be in
VSX.
A primary record will be created (and has been created for a few stars) with
links to the other catalogues when relevant. The primary record will show
the best data available for a given star. But this process takes a lot of
time and the user has to choose among the different entries by now.
GCVS entries have been given precedence (I mean if a revision of a star is
made it will be made to the GCVS entry and not to the ASAS or NSVS entry)
since they have the official names and include most of the variable stars.

So, going back to the errors you found. We have followed the policy of
keeping the original remarks as they are in the source catalogue so I would
suggest that you go to the Additional remark section and add a remark with
what you found and the correct reference.

We could discuss with Chris and all the people if that is the best thing to
do.

Best wishes,
Sebastian.

> Just a note on the consistency of the error... I just took a quick
> look at RW CEP and find the same type of mis-direction at least for 2
> of these that the Study ref. points to the Harvard Annals. This one
> also points to Milton Field 27 abstract and it should point to Milton
> Field 9.
>
> ... hope this is doing some good.
>
> Rick
>
> --- In vsx-dis@yahoogroups.com, "rcdegraeve" <rcdegraeve@...> wrote:
>>
>> Hello Chris,
>>
>> I apologize for not including the info in my original post but I
>> wasn't sure it would be okay.
>>
>> Anyway...
>>
>> My interest is mostly an Miras and SRs. Looking into some SRs in
>> Cephus I came across an what may be inaccurate info in VSX for AN
> CEP
>> (haven't had time to look into any more). The "Study ref." in the
>> database notes "C.Payne-Gaposchkin HA 118, N27, 1952."  Now, this
>> information as text only is correct as far as it goes (since it
>> doesn't reference the field). The problem seems to be where it
>> points. When following the hot spot, it takes you to the abstract
> for
>> Milton Field 27, which covers stars in Hydra, Leo and Sextans.
>> Digging a little deeper in the Harvard Annals, I found that, though
>> AN CEP is, indeed,  in vol 118, No. 27, it is in the abstract for
>> Milton Field 1, not 27. I'm guessing it could be a
> misinterpertation
>> of the "N27".
>>
>> It could be possible that I'm misinterperting what I see but I
>> thought I'd bring it up the the discussion group. I hope this
> doesn't
>> send anyone off on any wild goose chases!
>>
>> Rick De Graeve
>>
>>
>> --- In vsx-dis@yahoogroups.com, "Christopher Watson" <skygeex@>
>> wrote:
>> >
>> > Hi Rick,
>> >
>> > To tell you the truth, I'd rather you didn't save the details for
>> > actual submission.  Please give me an example of what you're
> talking
>> > about.  If this is a systemic problem, I'll want to find a back-
> end
>> > solution to it, rather than relying on user submissions of
> corrected
>> > data.  If it's something very localized, then user submissions
> may
>> be
>> > OK.  But I'd like to make that decision first.  So please show me
>> what
>> > you've got.  Thanks!
>> >
>> > Christopher Watson
>> > Principal Architect
>> > VSX
>> >
>> > On 5/2/07, rcdegraeve <rcdegraeve@> wrote:
>> > > I'm wondering about how to submit what I guess amounts to data
>> > > corrections to VSX. Reading through the guidelines, they seem
> to
>> focus
>> > > on submission of a new variable star and what/how to include
>> supporting
>> > > data.
>> > >
>> > > In looking through VSX and some of the reference information
>> cited in
>> > > an entry, I've found a nested inaccuracy in the Study ref. data
>> entry.
>> > > It's probably a just a small detail (and maybe I'm reading it
>> wrong)
>> > > but I know you want the database to be as accurate as
> possible.
>> I'll
>> > > save the details for actual submission, but I'm not too clear
> on
>> how to
>> > > go about this.
>> > >
>> > > Thanks for your help!
>> > >
>> > > Rick De Graeve
>> > > AAVSO - DGR
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > Yahoo! Groups Links
>> > >
>> > >
>> > >
>> > >
>> >
>>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
> El mail recibido, fue verificado por el Servicio de Antivirus para mail de
> Fullzero
> y se encuentra libre de virus
>
>

Hi Rick,

The text references are the original GCVS references.  These have been put
through the ADS resolver to attach bibcodes to them.  Since the GCVS
references are not written according to the standard ADS format, sometimes
they needed a couple of tweaks so that the ADS resolver could understand
them (e.g. the abbreviation needed changing for some journals).  In some
cases, such as these, misinterpretations by the ADS resolver results in
wrong bibcodes.  So these need to be corrected.  In the cases you found
the bibcodes should be 1952AnHar.118..147P for Field 9 and
1952AnHar.118..217P for field 27.  These will have to be corrected in the
database themselves, there is no way to correct them through the user
interface.
Thanks for the corrections!

Patrick

--- rcdegraeve <rcdegraeve@...> wrote:

> Just a note on the consistency of the error... I just took a quick
> look at RW CEP and find the same type of mis-direction at least for 2
> of these that the Study ref. points to the Harvard Annals. This one
> also points to Milton Field 27 abstract and it should point to Milton
> Field 9.
>
> ... hope this is doing some good.
>
> Rick
>
> --- In vsx-dis@yahoogroups.com, "rcdegraeve" <rcdegraeve@...> wrote:
> >
> > Hello Chris,
> >
> > I apologize for not including the info in my original post but I
> > wasn't sure it would be okay.
> >
> > Anyway...
> >
> > My interest is mostly an Miras and SRs. Looking into some SRs in
> > Cephus I came across an what may be inaccurate info in VSX for AN
> CEP
> > (haven't had time to look into any more). The "Study ref." in the
> > database notes "C.Payne-Gaposchkin HA 118, N27, 1952."  Now, this
> > information as text only is correct as far as it goes (since it
> > doesn't reference the field). The problem seems to be where it
> > points. When following the hot spot, it takes you to the abstract
> for
> > Milton Field 27, which covers stars in Hydra, Leo and Sextans.
> > Digging a little deeper in the Harvard Annals, I found that, though
> > AN CEP is, indeed,  in vol 118, No. 27, it is in the abstract for
> > Milton Field 1, not 27. I'm guessing it could be a
> misinterpertation
> > of the "N27".
> >
> > It could be possible that I'm misinterperting what I see but I
> > thought I'd bring it up the the discussion group. I hope this
> doesn't
> > send anyone off on any wild goose chases!
> >
> > Rick De Graeve
> >
> >
> > --- In vsx-dis@yahoogroups.com, "Christopher Watson" <skygeex@>
> > wrote:
> > >
> > > Hi Rick,
> > >
> > > To tell you the truth, I'd rather you didn't save the details for
> > > actual submission.  Please give me an example of what you're
> talking
> > > about.  If this is a systemic problem, I'll want to find a back-
> end
> > > solution to it, rather than relying on user submissions of
> corrected
> > > data.  If it's something very localized, then user submissions
> may
> > be
> > > OK.  But I'd like to make that decision first.  So please show me
> > what
> > > you've got.  Thanks!
> > >
> > > Christopher Watson
> > > Principal Architect
> > > VSX
> > >
> > > On 5/2/07, rcdegraeve <rcdegraeve@> wrote:
> > > > I'm wondering about how to submit what I guess amounts to data
> > > > corrections to VSX. Reading through the guidelines, they seem
> to
> > focus
> > > > on submission of a new variable star and what/how to include
> > supporting
> > > > data.
> > > >
> > > > In looking through VSX and some of the reference information
> > cited in
> > > > an entry, I've found a nested inaccuracy in the Study ref. data
> > entry.
> > > > It's probably a just a small detail (and maybe I'm reading it
> > wrong)
> > > > but I know you want the database to be as accurate as
> possible.
> > I'll
> > > > save the details for actual submission, but I'm not too clear
> on
> > how to
> > > > go about this.
> > > >
> > > > Thanks for your help!
> > > >
> > > > Rick De Graeve
> > > > AAVSO - DGR
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
>
>


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

I will most likely continue digging in the database. So... Is noting
the discrepancies here in the discussion database the preferred
method for getting the information to you? Would an email be better?
Also would you prefer that I hold all of the errors of this nature I
find until I am finished.  Assuming I find more of these errors, I
want to be sure I do this in the way you most prefer.

Thanks!
Rick

--- In vsx-dis@yahoogroups.com, Patrick Wils <patrickwils@...> wrote:
>
> Hi Rick,
>
> The text references are the original GCVS references.  These have
been put
> through the ADS resolver to attach bibcodes to them.  Since the GCVS
> references are not written according to the standard ADS format,
sometimes
> they needed a couple of tweaks so that the ADS resolver could
understand
> them (e.g. the abbreviation needed changing for some journals).  In
some
> cases, such as these, misinterpretations by the ADS resolver
results in
> wrong bibcodes.  So these need to be corrected.  In the cases you
found
> the bibcodes should be 1952AnHar.118..147P for Field 9 and
> 1952AnHar.118..217P for field 27.  These will have to be corrected
in the
> database themselves, there is no way to correct them through the
user
> interface.
> Thanks for the corrections!
>
> Patrick
>
> --- rcdegraeve <rcdegraeve@...> wrote:
>
> > Just a note on the consistency of the error... I just took a
quick
> > look at RW CEP and find the same type of mis-direction at least
for 2
> > of these that the Study ref. points to the Harvard Annals. This
one
> > also points to Milton Field 27 abstract and it should point to
Milton
> > Field 9.
> >
> > ... hope this is doing some good.
> >
> > Rick
> >
> > --- In vsx-dis@yahoogroups.com, "rcdegraeve" <rcdegraeve@> wrote:
> > >
> > > Hello Chris,
> > >
> > > I apologize for not including the info in my original post but
I
> > > wasn't sure it would be okay.
> > >
> > > Anyway...
> > >
> > > My interest is mostly an Miras and SRs. Looking into some SRs
in
> > > Cephus I came across an what may be inaccurate info in VSX for
AN
> > CEP
> > > (haven't had time to look into any more). The "Study ref." in
the
> > > database notes "C.Payne-Gaposchkin HA 118, N27, 1952."  Now,
this
> > > information as text only is correct as far as it goes (since it
> > > doesn't reference the field). The problem seems to be where it
> > > points. When following the hot spot, it takes you to the
abstract
> > for
> > > Milton Field 27, which covers stars in Hydra, Leo and Sextans.
> > > Digging a little deeper in the Harvard Annals, I found that,
though
> > > AN CEP is, indeed,  in vol 118, No. 27, it is in the abstract
for
> > > Milton Field 1, not 27. I'm guessing it could be a
> > misinterpertation
> > > of the "N27".
> > >
> > > It could be possible that I'm misinterperting what I see but I
> > > thought I'd bring it up the the discussion group. I hope this
> > doesn't
> > > send anyone off on any wild goose chases!
> > >
> > > Rick De Graeve
> > >
> > >
> > > --- In vsx-dis@yahoogroups.com, "Christopher Watson" <skygeex@>
> > > wrote:
> > > >
> > > > Hi Rick,
> > > >
> > > > To tell you the truth, I'd rather you didn't save the details
for
> > > > actual submission.  Please give me an example of what you're
> > talking
> > > > about.  If this is a systemic problem, I'll want to find a
back-
> > end
> > > > solution to it, rather than relying on user submissions of
> > corrected
> > > > data.  If it's something very localized, then user
submissions
> > may
> > > be
> > > > OK.  But I'd like to make that decision first.  So please
show me
> > > what
> > > > you've got.  Thanks!
> > > >
> > > > Christopher Watson
> > > > Principal Architect
> > > > VSX
> > > >
> > > > On 5/2/07, rcdegraeve <rcdegraeve@> wrote:
> > > > > I'm wondering about how to submit what I guess amounts to
data
> > > > > corrections to VSX. Reading through the guidelines, they
seem
> > to
> > > focus
> > > > > on submission of a new variable star and what/how to
include
> > > supporting
> > > > > data.
> > > > >
> > > > > In looking through VSX and some of the reference
information
> > > cited in
> > > > > an entry, I've found a nested inaccuracy in the Study ref.
data
> > > entry.
> > > > > It's probably a just a small detail (and maybe I'm reading
it
> > > wrong)
> > > > > but I know you want the database to be as accurate as
> > possible.
> > > I'll
> > > > > save the details for actual submission, but I'm not too
clear
> > on
> > > how to
> > > > > go about this.
> > > > >
> > > > > Thanks for your help!
> > > > >
> > > > > Rick De Graeve
> > > > > AAVSO - DGR
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Yahoo! Groups Links
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> >
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>

Hi Rick,

You probably best send those errors to Chris and/or me.  You may choose
when to send them, I don't have a preference.
For some of the GCVS references there isn't a bibcode or link-out in VSX
yet, either because it does not exist or because we haven't found one.  If
you find some of these, let us know as well.

Thanks for your efforts.

Patrick

--- rcdegraeve <rcdegraeve@...> wrote:

> I will most likely continue digging in the database. So... Is noting
> the discrepancies here in the discussion database the preferred
> method for getting the information to you? Would an email be better?
> Also would you prefer that I hold all of the errors of this nature I
> find until I am finished.  Assuming I find more of these errors, I
> want to be sure I do this in the way you most prefer.
>
> Thanks!
> Rick


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

VSX doesn't seem to be working when I try to access it from an AAVSO
lightcurve. (Monday PM)

Martin Nicholson NMR

It looks to me as if there are 1500-1600 variable stars in the
International Variable Star Index that have the prefix VSX.

Does the AAVSO have any plans to publish these discoveries and hence
get them listed in Simbad?

> Does the AAVSO have any plans to publish these discoveries and hence
> get them listed in Simbad?

Yes. We're working on it.

I fully expect to see Greaves jump in here now, so hold on...

Christopher Watson
Principal Architect
VSX

Since Martin was involved in the email discussion a couple of months ago where
the answer to this question was discussed at length, I'd call this posting a
troll.  Martin, can you please not try to stir the pot?

-Walt

---- skygxproject <skygeex@...> wrote:
> > Does the AAVSO have any plans to publish these discoveries and hence
> > get them listed in Simbad?
>
> Yes. We're working on it.
>
> I fully expect to see Greaves jump in here now, so hold on...
>
> Christopher Watson
> Principal Architect
> VSX
>
>
>
>
> Yahoo! Groups Links
>
>
>

Not at all - a few months have gone by without any news so I asked
for an update.




--- In vsx-dis@yahoogroups.com, <waltc@...> wrote:
>
> Since Martin was involved in the email discussion a couple of
months ago where the answer to this question was discussed at length,
I'd call this posting a troll.  Martin, can you please not try to
stir the pot?
>
> -Walt
>
> ---- skygxproject <skygeex@...> wrote:
> > > Does the AAVSO have any plans to publish these discoveries and
hence
> > > get them listed in Simbad?
> >
> > Yes. We're working on it.
> >
> > I fully expect to see Greaves jump in here now, so hold on...
> >
> > Christopher Watson
> > Principal Architect
> > VSX
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
>

I think a billion author paper is warranted in this case.

M.


On May 23, 2007, at 8:55 AM, star.vars wrote:

> Billion author papers ain't unprecedented nowadays.

In the case of IBVS I think it's due to the change in editorial policy, not VSX.

On 5/25/07, skepticalones <skepticalones@...> wrote:
> --- In vsx-dis@yahoogroups.com, "hannahvarleyfromdublin"
> <hannahvarleyfromdublin@...> wrote:
>
> > VSX has clearly made a VERY substantial contribution to the total
> > amount of refereed variable star material published and whatever
> > supporting infrastructure that is put in place needs to reflect this.
>
> Expand on this, with specific examples illustrating the point.
>
> I am aware of no evidence to support this statement, specifically
> within the context of published refereed variable star material either
> accrediting VSX or having VSX appelations.  You make this statement of
> fact yet provide no evidence, especially contradictory as you had just
> previously reported that next to nothing was being published in
> several of the usual venues for such material.
>
> John
>
>
>
>
> Yahoo! Groups Links
>
>
>
>


--
----------------------------------------
Jim Bedient
jbedient@...
www.bedient.us

FYI: The Membership setting for this group is now set to Restricted,
and all Joins must now be approved by the Owner. This should cause no
inconvenience for our current members, but please do let me know
PRIVATELY if the new settings give rise to any problems for you.

Christopher

The JAAVSO has been more active, it seems to me, as well:

http://www.aavso.org/publications/ejaavso/index.shtml

As a personal aside, I will never again submit a paper to the IBVS. I
think they suck ass. I have several papers in the works that will go
either to JAAVSO or PASP.

M.


On May 25, 2007, at 3:18 PM, James Bedient wrote:

> In the case of IBVS I think it's due to the change in editorial
> policy, not VSX.

> http://www.aavso.org/publications/ejaavso/index.shtml
>
> As a personal aside, I will never again submit a paper to the IBVS. I
> think they suck ass. I have several papers in the works that will go
> either to JAAVSO or PASP.

It is hard to understand why they ask for things of astrophysical interest
only and they ban data-mining results and however they publish photometric
sequences for novae and times of minima for anything.

Cheers,
Sebastian.

There might be an issue with the new variable submission facility. It
is not clear that a submission made today worked - error message in
Internet Explorer.

I mentioned this to the principal architect a few months ago. It is a
request that may be of help only to me.  I am doing a drift-scan
survey with a small scope and small ccd. The images are about 15' in
dec. The ra size can be many degrees.  I would liike to be able to
search the database in an efficient way for this.  At present it seems
only circular or square box searches are possible using ra/dec.  It
would be nice to ask for a rectangular box, with reasonable limits on
the size of course.
Might this be possible?

Thanks,

Jim

Hi Jim,

Yes, that enhancement is in the Bugzilla database, and as soon as I
can make it through some other AAVSO obligations, I'll be looking into
implementing a few of these types of features.

Thanks for your very good suggestion.

Christopher Watson
Principal Architect
VSX

On 5/28/07, Jim Cadien <jcadien1@...> wrote:
> I mentioned this to the principal architect a few months ago. It is a
> request that may be of help only to me.  I am doing a drift-scan
> survey with a small scope and small ccd. The images are about 15' in
> dec. The ra size can be many degrees.  I would liike to be able to
> search the database in an efficient way for this.  At present it seems
> only circular or square box searches are possible using ra/dec.  It
> would be nice to ask for a rectangular box, with reasonable limits on
> the size of course.
> Might this be possible?
>
> Thanks,
>
> Jim
>
>
>
> Yahoo! Groups Links
>
>
>
>

Is there an unpublished version of Brian Skiff's MKTypes.dat file
floating around?  I was looking at a couple of stars I put in, and
"Admin, VSX" amended them with a spectral type - but when I looked in
the source given in the new reference
(http://vizier.u-strasbg.fr/viz-bin/Cat?III/233B) there's nothing
there.  Example is VSX J075901.6-395126,
http://www.aavso.org/vsx/index.php?view=detail.top&oid=135934.

In addition the bibcode given in the reference is out of date,
1993yCat.3170.....M, should be 2004yCat.3233....0S

Jim

----------------------------------------
Jim Bedient
jbedient@...
www.bedient.us

You can find an up-to-date versiob of Brian Skiff's file here:
<ftp://ftp.lowell.edu/pub/bas/starcats/mktypes.dat> (see details here:
<http://adsabs.harvard.edu/cgi-bin/nph-bib_query?bibcode=2004yCat.3233....0S>.)
  The version used in VSX dates from November 2006.  The bibcode used in
VSX is the bibcode of the original source publication.  In some cases
Brian "invented" bibcodes for catalogs at VizieR which are not available
through ADS.  1993yCat.3170.....M is such a case, it refers to
<http://cdsarc.u-strasbg.fr/viz-bin/Cat?III/170>.  See
<http://vizier.cfa.harvard.edu/viz-bin/VizieR-5?-out.add=.&-source=III/170/ps_id\
&recno=2904>
for this specific star.

Patrick

--- James Bedient <jbedient@...> wrote:

> Is there an unpublished version of Brian Skiff's MKTypes.dat file
> floating around?  I was looking at a couple of stars I put in, and
> "Admin, VSX" amended them with a spectral type - but when I looked in
> the source given in the new reference
> (http://vizier.u-strasbg.fr/viz-bin/Cat?III/233B) there's nothing
> there.  Example is VSX J075901.6-395126,
> http://www.aavso.org/vsx/index.php?view=detail.top&oid=135934.
>
> In addition the bibcode given in the reference is out of date,
> 1993yCat.3170.....M, should be 2004yCat.3233....0S
>
> Jim
>
> ----------------------------------------
> Jim Bedient
> jbedient@...
> www.bedient.us
>




________________________________________________________________________________\
____Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/

When Skiff's MKTypes.dat file info was input to VSX, some of the
positions, which were used to override the existing positions, were
put in incorrectly.

Example:

VSX J084716.7-471324

Position I gave:          08 47 16.77 -47 13 24.6
Position in Skiff's file: 08 47 16.77 -47 13 24.6
(No shock, same source, UCAC2)

Position in VSX, attributed to Skiff: 08 47 16.70 -47 13 24.6

The ones I've looked at have all had the last decimal place of RA changed to 0.

OK, it's only 0.07" of RA, but the correct numbers are the correct numbers.

Jim

no surprise,
On 5/29/07, Patrick Wils <patrickwils@...> wrote:
> You can find an up-to-date versiob of Brian Skiff's file here:
> <ftp://ftp.lowell.edu/pub/bas/starcats/mktypes.dat> (see details here:
>
<http://adsabs.harvard.edu/cgi-bin/nph-bib_query?bibcode=2004yCat.3233....0S>.)
>  The version used in VSX dates from November 2006.  The bibcode used in
> VSX is the bibcode of the original source publication.  In some cases
> Brian "invented" bibcodes for catalogs at VizieR which are not available
> through ADS.  1993yCat.3170.....M is such a case, it refers to
> <http://cdsarc.u-strasbg.fr/viz-bin/Cat?III/170>.  See
>
<http://vizier.cfa.harvard.edu/viz-bin/VizieR-5?-out.add=.&-source=III/170/ps_id\
&recno=2904>
> for this specific star.
>
> Patrick
>
> --- James Bedient <jbedient@...> wrote:
>
> > Is there an unpublished version of Brian Skiff's MKTypes.dat file
> > floating around?  I was looking at a couple of stars I put in, and
> > "Admin, VSX" amended them with a spectral type - but when I looked in
> > the source given in the new reference
> > (http://vizier.u-strasbg.fr/viz-bin/Cat?III/233B) there's nothing
> > there.  Example is VSX J075901.6-395126,
> > http://www.aavso.org/vsx/index.php?view=detail.top&oid=135934.
> >
> > In addition the bibcode given in the reference is out of date,
> > 1993yCat.3170.....M, should be 2004yCat.3233....0S
> >
> > Jim
> >
> > ----------------------------------------
> > Jim Bedient
> > jbedient@...
> > www.bedient.us
> >
>
>
>
>
>
________________________________________________________________________________\
____Pinpoint customers who are looking for what you sell.
> http://searchmarketing.yahoo.com/
>
>
>
> Yahoo! Groups Links
>
>
>
>


--
----------------------------------------
Jim Bedient
jbedient@...
www.bedient.us

> When Skiff's MKTypes.dat file info was input to VSX, some of the
> positions, which were used to override the existing positions, were
> put in incorrectly.
>
> The ones I've looked at have all had the last decimal place of RA changed to
0.

Looks like you are correct, Jim.  These new positions were part of the
batch imports created by Patrck.  I'll check in with him on this.

Thanks for pointing this out.

-Chris

Yes, it seems I lost a decimal in RA.  I'll correct this.

Patrick

--- James Bedient <jbedient@...> wrote:

> When Skiff's MKTypes.dat file info was input to VSX, some of the
> positions, which were used to override the existing positions, were
> put in incorrectly.
>
> Example:
>
> VSX J084716.7-471324
>
> Position I gave:          08 47 16.77 -47 13 24.6
> Position in Skiff's file: 08 47 16.77 -47 13 24.6
> (No shock, same source, UCAC2)
>
> Position in VSX, attributed to Skiff: 08 47 16.70 -47 13 24.6
>
> The ones I've looked at have all had the last decimal place of RA
> changed to 0.
>
> OK, it's only 0.07" of RA, but the correct numbers are the correct
> numbers.
>
> Jim
>
> no surprise,
> On 5/29/07, Patrick Wils <patrickwils@...> wrote:
> > You can find an up-to-date versiob of Brian Skiff's file here:
> > <ftp://ftp.lowell.edu/pub/bas/starcats/mktypes.dat> (see details here:
> >
>
<http://adsabs.harvard.edu/cgi-bin/nph-bib_query?bibcode=2004yCat.3233....0S>.)
> >  The version used in VSX dates from November 2006.  The bibcode used
> in
> > VSX is the bibcode of the original source publication.  In some cases
> > Brian "invented" bibcodes for catalogs at VizieR which are not
> available
> > through ADS.  1993yCat.3170.....M is such a case, it refers to
> > <http://cdsarc.u-strasbg.fr/viz-bin/Cat?III/170>.  See
> >
>
<http://vizier.cfa.harvard.edu/viz-bin/VizieR-5?-out.add=.&-source=III/170/ps_id\
&recno=2904>
> > for this specific star.
> >
> > Patrick
> >
> > --- James Bedient <jbedient@...> wrote:
> >
> > > Is there an unpublished version of Brian Skiff's MKTypes.dat file
> > > floating around?  I was looking at a couple of stars I put in, and
> > > "Admin, VSX" amended them with a spectral type - but when I looked
> in
> > > the source given in the new reference
> > > (http://vizier.u-strasbg.fr/viz-bin/Cat?III/233B) there's nothing
> > > there.  Example is VSX J075901.6-395126,
> > > http://www.aavso.org/vsx/index.php?view=detail.top&oid=135934.
> > >
> > > In addition the bibcode given in the reference is out of date,
> > > 1993yCat.3170.....M, should be 2004yCat.3233....0S
> > >
> > > Jim
> > >
> > > ----------------------------------------
> > > Jim Bedient
> > > jbedient@...
> > > www.bedient.us
> > >
> >
> >
> >
> >
> >
>
________________________________________________________________________________\
____Pinpoint
> customers who are looking for what you sell.
> > http://searchmarketing.yahoo.com/
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>
>
> --
> ----------------------------------------
> Jim Bedient
> jbedient@...
> www.bedient.us
>




________________________________________________________________________________\
____
Sucker-punch spam with award-winning protection.
Try the free Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/features_spam.html

Patrick Wils wrote:
> ASAS 183136-1815.4 was found to be a Mira type variable with a period of
> 209 days (range 12.3-<14.3V) by ASAS3.
> Brian Skiff's MKTypes.dat file of spectral types contains an entry for
> SS73 167 = UCAC2 24932494 (mag 14.5V), 4.7" from the position of the ASAS
> star (and the precision of the ASAS coordinates is only 6").   SS73 167 is
> a Be star (the source is
> <http://cdsads.u-strasbg.fr/cgi-bin/nph-bib_query?1973ApJ...185..899S>).
> If this is not a chance alignment, and both stars are thus physically
> related, and the Be classification is correct, this might be a symbiotic
> binary.  Is anyone interested in investigating this further?
>
  From MKTypes.dat, the coordinates for SS73 167 = UCAC2 24932494 are:
1973ApJ...185..899S  SS73 167                18 31 36.30 -18 15 25.9 U 14.5 V 
Be

I took UBVRI images of this field during my last NOFS observing
run a couple of weeks ago.  This source is present at
      RA (J2000) DEC          V     B-V    V-Rc   Rc-Ic  V-Ic
18:31:36.29  -18:15:26.0  15.097  2.636  2.020  2.090  4.125
and absent on my U-band image (pretty reddened region in Sgr).
I see no indication that this is a Be star; looks like a typical
red star to me.

I've placed 2x2 arcmin images centered on this object at:
http://www.aavso.org/tmp2/asasi.jpg
http://www.aavso.org/tmp2/asasr.jpg
http://www.aavso.org/tmp2/asasv.jpg
http://www.aavso.org/tmp2/asasb.jpg
http://www.aavso.org/tmp2/asasu.jpg
(sorry about the seeing, but it is never great with the 1.0m)

Sanduleak and Stephenson's coordinates and information are:
star   RA (B1950) DEC        p     v   n type
167  18:28:40.7 -18:17:40  14.0  12.0  5 Be! new
where Be! indicates extreme Be-like object, and n is the last
resolvable hydrogen line in the emission spectrum.  Coordinates were
derived from measures made on the objective prism plates and should
be reliable to within several seconds of arc.

Straight precession of the SS coordinates is
18:31:36.3 -18:15:29

All in all, it looks like either the SS catalog picked the wrong
object, or they caught a symbiotic system in outburst; that
would agree with their estimate of mv=12.  Nothing in the field
is particularly blue.
Arne

> All in all, it looks like either the SS catalog picked the wrong
> object, or they caught a symbiotic system in outburst; that
> would agree with their estimate of mv=12.

The mv=12 may correspond to the maximum magnitude of the Mira star as well
(see
<http://www.astrouw.edu.pl/cgi-gp/asas_plot_raw_all?183136-1815.4,asas3,0,500,0>
and <http://skydot.lanl.gov/nsvs/star.php?num=16676109&mask=15636>).  You
likely observed the Mira star near minimum, Arne.
A lot of the Be stars from SS73 have been recovered during other surveys,
but not this one.  There is always a chance of a typo in the catalog
coordinates of course (and it seems that way here), but what are the odds
it then corresponds to within 5" of a Mira variable?

Patrick


--- arne <arne@...> wrote:

> Patrick Wils wrote:
> > ASAS 183136-1815.4 was found to be a Mira type variable with a period
> of
> > 209 days (range 12.3-<14.3V) by ASAS3.
> > Brian Skiff's MKTypes.dat file of spectral types contains an entry for
> > SS73 167 = UCAC2 24932494 (mag 14.5V), 4.7" from the position of the
> ASAS
> > star (and the precision of the ASAS coordinates is only 6").   SS73
> 167 is
> > a Be star (the source is
> >
> <http://cdsads.u-strasbg.fr/cgi-bin/nph-bib_query?1973ApJ...185..899S>).
>
> > If this is not a chance alignment, and both stars are thus physically
> > related, and the Be classification is correct, this might be a
> symbiotic
> > binary.  Is anyone interested in investigating this further?
> >
>  From MKTypes.dat, the coordinates for SS73 167 = UCAC2 24932494 are:
> 1973ApJ...185..899S  SS73 167                18 31 36.30 -18 15 25.9 U
> 14.5 V  Be
>
> I took UBVRI images of this field during my last NOFS observing
> run a couple of weeks ago.  This source is present at
>      RA (J2000) DEC          V     B-V    V-Rc   Rc-Ic  V-Ic
> 18:31:36.29  -18:15:26.0  15.097  2.636  2.020  2.090  4.125
> and absent on my U-band image (pretty reddened region in Sgr).
> I see no indication that this is a Be star; looks like a typical
> red star to me.
>
> I've placed 2x2 arcmin images centered on this object at:
> http://www.aavso.org/tmp2/asasi.jpg
> http://www.aavso.org/tmp2/asasr.jpg
> http://www.aavso.org/tmp2/asasv.jpg
> http://www.aavso.org/tmp2/asasb.jpg
> http://www.aavso.org/tmp2/asasu.jpg
> (sorry about the seeing, but it is never great with the 1.0m)
>
> Sanduleak and Stephenson's coordinates and information are:
> star   RA (B1950) DEC        p     v   n type
> 167  18:28:40.7 -18:17:40  14.0  12.0  5 Be! new
> where Be! indicates extreme Be-like object, and n is the last
> resolvable hydrogen line in the emission spectrum.  Coordinates were
> derived from measures made on the objective prism plates and should
> be reliable to within several seconds of arc.
>
> Straight precession of the SS coordinates is
> 18:31:36.3 -18:15:29
>
> All in all, it looks like either the SS catalog picked the wrong
> object, or they caught a symbiotic system in outburst; that
> would agree with their estimate of mv=12.  Nothing in the field
> is particularly blue.
> Arne
>




________________________________________________________________________________\
____
Sick sense of humor? Visit Yahoo! TV's
Comedy with an Edge to see what's on, when.
http://tv.yahoo.com/collections/222

Patrick Wils wrote:
>>All in all, it looks like either the SS catalog picked the wrong
>>object, or they caught a symbiotic system in outburst; that
>>would agree with their estimate of mv=12.
>
>
> The mv=12 may correspond to the maximum magnitude of the Mira star as well
> (see
>
<http://www.astrouw.edu.pl/cgi-gp/asas_plot_raw_all?183136-1815.4,asas3,0,500,0>
> and <http://skydot.lanl.gov/nsvs/star.php?num=16676109&mask=15636>).  You
> likely observed the Mira star near minimum, Arne.
> A lot of the Be stars from SS73 have been recovered during other surveys,
> but not this one.  There is always a chance of a typo in the catalog
> coordinates of course (and it seems that way here), but what are the odds
> it then corresponds to within 5" of a Mira variable?
>
You may be correct about the Mira maximum; however, I based my
comment on the fact that it was brighter than when I observed it,
and showed strong emission lines.  There is no evidence of strong
emission in my photometry; for example, Rc seems to be perfectly
normal.

I'll ask Ulisse to get a spectrum as a final check.
Arne

Is there an issue with the computers at HQ?

Just recently the links from lightcurves to VSX seem to fail about one
time in ten and Web Obs has been giving an error message (error opening
ccdfile: Undefined index: ccdfileSorry, could not process that file) at
gradually more frequent intervals - it has also been doing this full-
time for a couple of days for sure<g>!