I get this error when trying to stack 4 images.
Server Error in '/app' Application.
Index was outside the bounds of the array.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IndexOutOfRangeException: Index was outside the bounds of the array.
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 was outside the bounds of the array.]
Restricted_Files5.lbtnStack_Click(Object sender, EventArgs e) +2004
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) +9672326
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.34249
Michael:
Open each image and see if you get a normal photometric result for each?
If you share them with me (MZK) I can take a look. Also share sequence.
Ken
PS: I just stacked four of my images to check system. Stacking worked normally.
Confusing here indeed, this term "stack" has two different meanings! "Stacking" images vs. the computers "stack" memory space! The latter is apparently what has been exceeded, and is a very common error. An array in Vphot hasn't been allocated enough space to handle the operations needed in the image "stacking" operation.
The obvious solution is to allocate the arrays needed on the heap, using the "new" operator, or "vector" class, which allows dynamic allocation of as much space is needed (up to the physical memory available on the system) without fatal system errors like this.
You still need to check on how much memory the user's input is requesting, though. The program needs to handle all cases, even if the user does something "wrong", but to gracefully exit, rather than crash ;)
Mike
This looks like a problem that will need investigating when I get back from my travels; currently camping my away across the continent.
An indexoutofrange error sounds like a program bug.
Please share the 4 images you were trying to stack with me (SGEO) when the error was precipitated. I will followup as soon as I can.
George
My apologies George, Ken et. al. One of the images was missing WCS, and that was the cause of the VPhot error message. Once I excluding that image, the other images stacked. I just didn't notice the honking RED square dot in the WCS column of my images List. I'm getting my eyes checked tomorrow ;-)
Michael