[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Name-List 77 contains TASS variable
I guess that what I meant was that being able to do something like "select *
from <table> where wsstat(<star id>) > 100" would be what I'd want. Of
course, instead of making some wsstat() function to calculate the W-S stats
on the fly, it could/should actually be a separate table with <id> and
<wsstat> that gets updated whenever new data is inserted. Given my meager
SQL skills, if I want to do this currently I have to pull all of the data
for a star that I somehow think might be variable, and run it through a W-S
calculator here. A bit tedious when your talking millions of stars.
Tom's semi-manual process of calculating the W-S stats, reviewing the
information, and posting it out via email works as well, but I'm sure Tom
would rather that the rest of us get busy doing some of the work!
Shawn
----- Original Message -----
From: "Chris Albertson" <chrisalbertson90278@yahoo.com>
To: "Shawn Dvorak (Rolling Hills Obs)" <rollinghillsobs@cfl.rr.com>; "TASS
List" <TASS@listserv.wwa.com>
Sent: Tuesday, June 03, 2003 2:24 AM
Subject: Re: Name-List 77 contains TASS variable
>
> --- "Shawn Dvorak (Rolling Hills Obs)" <rollinghillsobs@cfl.rr.com>
> wrote:
> > ...My experience with the Mark III
> > database was that it was way too slow to remotely pull large data
> > sets to do
> > things like search for stars with large W-S stats. Maybe this is
> > easier/faster now?
>
> Ah, I knew I could get some good information If I ask people who
> are actually doing work. Yes it will always be too slow to remotely
> pull large data sets as our idea of what is "large" keeps
> growing. The way to do a search is NOT to pull all
> the data then search it locally but to ask the database for
> "All the stars with (for example) a large W-S stat". Or maybe
> ask it for the "top 100 W-S that is between two RA values
> and two dec value and within some Magnitude limit.
> The idea is to NEVER transmit a large dataset.
>
> The database should be smart enough to accept fairly complex
> querries. So my question, again is what would you ask for?
> Almost anything is possable such as the result of some user
> defined function being within some limits, or, a cross ID to some
> "standard" catalog. Again the idea is that you do the
> "disk thrashing" on the database end.
>
> It is also possible to set up a "trap" or "trigger": Define
> an event or statistical relationship yu want to see and have
> it notify you when data meeting that criteria are stored.
> Modern data bases can do qute a bit of work for you.
>
>
>
> >
> > Shawn
> >
> > ----- Original Message -----
> > From: "Chris Albertson" <chrisalbertson90278@yahoo.com>
> > To: "Shawn Dvorak (Rolling Hills Obs)" <rollinghillsobs@cfl.rr.com>;
> > "TASS
> > List" <TASS@listserv.wwa.com>
> > Sent: Monday, June 02, 2003 8:55 PM
> > Subject: Re: Name-List 77 contains TASS variable
> >
> >
> > >
> > > --- "Shawn Dvorak (Rolling Hills Obs)" <rollinghillsobs@cfl.rr.com>
> > > wrote:
> > > > ... Of course, there's still lots of undiscovered variables in
> > > > the Mark III data, and a lot more in the Mark IV archives.
> > >
> > > What do you think is the main bottle neck in finding these?
> > > What would speed up the search through this data?
> > > I'm thinking about building some database search tools.
> > >
> > > =====
> > > Chris Albertson
> > > Home: 310-376-1029 chrisalbertson90278@yahoo.com
> > > Cell: 310-990-7550
> > > Office: 310-336-5189 Christopher.J.Albertson@aero.org
> > > KG6OMK
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> > > http://calendar.yahoo.com
> >
> >
>
>
> =====
> Chris Albertson
> Home: 310-376-1029 chrisalbertson90278@yahoo.com
> Cell: 310-990-7550
> Office: 310-336-5189 Christopher.J.Albertson@aero.org
> KG6OMK
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> http://calendar.yahoo.com