"Keep this" feature throws an error

Affiliation
American Association of Variable Star Observers (AAVSO)
Mon, 08/15/2016 - 15:25

When viewing my photometry report and deselecting the stars that are most problematic (red) then attempting to save the results via "Keep this" I get the error shown below.

At present, the only workaround is to write down the star IDs then go back to the image and click the "X" to delete them from the list there.  This is quite tedious so I'm hoping there is a fix for this.

Thanks, OJJ

 

"Exception Details: System.IndexOutOfRangeException: Index 0 is either negative or above rows count.

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace: 

[IndexOutOfRangeException: Index 0 is either negative or above rows count.]
   System.Data.DataView.GetRow(Int32 index) +5306573
   System.Data.DataView.get_Item(Int32 recordIndex) +12
   BL.Util.FindPrimaryTarget(Hashtable activeMeasurements, Int32 imgW, Int32 imgH) +831
   SingleImageReport.SaveToLog() +1077
   SingleImageReport.lbtnKeep_Click(Object sender, EventArgs e) +20
   System.Web.UI.WebControls.LinkButton.OnClick(EventArgs e) +116
   System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument) +101
   System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +10
   System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +13
   System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +9665034
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1724

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34280"

Affiliation
American Association of Variable Star Observers (AAVSO)
Keep This

John:

I assume you clicked refresh first?

It works normally and it worked a minute ago for me. No need for a fix? There was limited space in drive c:. Now cleaned out. That may have been the problem?

Ken

Affiliation
American Association of Variable Star Observers (AAVSO)
"Keep this" feature throws an error

Hi Ken,

Thanks for your quick reply.  Here's the steps I just tried.

1) In my image list, I clicked on one of my stacked images of M11.  

2) Once that image is displayed, I selected "Load AAVSO Standard stars".

3) Once aperatures are shown around all the standard stars I then click on "View Photometry Report".

4) Once the photometry report is displayed I deselect a few of the biggest (red) stars flagged in the report.

5) At this point I clicked on "Refresh".  After the refresh is complete I noted that the deselected stars are still deselected.

6) Last I click on "Keep this".  It is at that point that I just now got the same error as before: 

Exception Details: System.IndexOutOfRangeException: Index 0 is either negative or above rows count.

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

This is in Chrome: Version 52.0.2743.116 m.  I will try it in Firefox too and let you know.

Thanks again for your attention on this.

--John (OJJ)

 

Affiliation
American Association of Variable Star Observers (AAVSO)
"Keep this" feature throws an error in Vphot photometry report

I get the very same error in Firefox version 47.0 (Win 10 machine in all cases).

I suppose I should start a separate thread on this but Vphot is also very slow on some simple operations such as simply logging in or during refresh of my image list.  These two operations take 60 seconds or more to complete.

--John (OJJ)

Affiliation
American Association of Variable Star Observers (AAVSO)
Error

John:

1. Please share (to MZK) a stacked M11 image and the original images that were used to create the stack. This will allow me to work with them too. 

2. It is possible for VPhot to exhibit some issues when the number of comps is VERY large. The functional matrices just overwhelm the processing.

3. I suspect you are imaging M11 to run your transform coeffs? After going to the photometry page, I usually download the instrumental mag table. Why are you clicking "save this"? Are you trying to measure magnitudes of a target for some reason?

4. I can confirm that IF you are an active VPhot user AND you have a very large number of sequences and images, the log in process may take as long a 60+ secs. I have talked to George Silvis about this and we are trying to determine what causes this.

Let's try to figure this out?

Ken

Affiliation
American Association of Variable Star Observers (AAVSO)
"Share'd" M11 stacked images

Hi Ken, sorry but I hadn't realized that there was a feature in Vphot for "sharing" images until just now (I thought you literally meant to share via an email attachment).  So I've "Share'd" M11 stacked images (and M67 and NGC7790) with you.  Some of these I stacked natively in Vphot but others were stacked in MaxImDL.  The reason for the latter is that recently my M11 images wouldn't properly stack/register in Vphot.  It was the native Vphot stacks that always threw that error but I'm sure the others will too.

Unfortunately, before I saw your request to share the original images and in thinking that my many original images were slowing down the login and refresh I decided to delete them all.  I'll try to re-upload the M11 originals in the next few days.

As you correctly guessed; yes, these are for getting transform coefficients from the TG app.  Maybe this isn't the best way to do things but I've been downloaing ALL of the AAVSO standard stars, which obvously produces a cluttered mass of apertures. I then run the photometry report.  Now I have in the past simply downloaded that photometry report and then deleted outliers in the TG app but I'm assuming that the whole purpose of flagging the Red-Pinkish stars is to ID those apertures that are in crowded fields or have low S/N etc. is to allow a person to omit them and possibly go back to the image to inspect and repeat as necessary.  Since I can't seem to save the deselected stars via the "Keep this" feature, I've had to resort to writing down which stars were problematic (red-pink) and then going back to the image and "X-ing" them out that way. It's pretty tedious but since I can't seem to save the modified photometry report I don't know how else to do it.

To make matters worse, even if I deselect problem stars in the photmetry report then download the report, those same stars still show up as "true" in the "estimate active" column of the report.  So this all beggs the question, how does a person omit problem stars from the photometry report?  It can be tediously done via the list on the Image page but as far as I can tell not the Photometry report page.

--John 

 

Affiliation
American Association of Variable Star Observers (AAVSO)
Problems with M11 Standard Field

John:

When Arne completed calibration of the M11 field and made it available as an AAVSO Standard Stars Field, we immediately saw some problems due to the number of comps (twice as many as for M67 and NGC7790!). Both VSP and VPhot exhibited some problems. In VSP, one had to select a small magnitude range and FOV to get them to plot without an error. VPhot can import them but working through normal operations is unfortunately also impacted by the number of comps.

I will check your stacking problem when you share the original images. I do not need many.

However, your note of the tedious effort to keep track of the comps and delete them from the comp list by X-ing them out is apparent to me also. sad You only need to do it once and save the better (smaller) sequence but it is still annoying. Once done, it could be shared with everyone else!! smiley

There are some alternatives that you already tried? Just leave the entire list in the file you download and import into TG. Remove the outliers in TG on the graph. This seems to work. Did it do so for you? Another is just to use M67 and NGC7790 for your transform coefficients. They are at a better airmass for you anyway!? This does not help our southern friends!

I will play around with this too. I recommend we talk off-line (or Skype) and just post a conclusion when we finish? You have my email address from other private emails?

Ken

 

Affiliation
American Association of Variable Star Observers (AAVSO)
Problems with M11 Standard Field

Ken,  

As mentioned previously, I did share all of my Vphot images with you.  Also, I did share my email address with you via the "contact" link provided in your AAVSO profile page.  Let me know if you haven't received it and I'll try again.  Or send yours via my AAVSO contact info. 

Also, I originally did just what you suggested; that is, I simply downloaded the un-scrubbed photometry report then removed the outliers in TG.  I'm a a little suspicious of this but will compare it to a throughly scrubbed photometry report.  And as you say, you only need create one template of good stars then you don't have to do it again.

Thanks again,

John (OJJ)

Affiliation
American Association of Variable Star Observers (AAVSO)
Sent MKZ a message

Hi Ken,

It doesn't look like I can attach a .FITs file here so I sent you a message via "Contact MKZ" and included my email address.  I'll attach my M11 image via email once I have yours.

John