VPHOT Transform Applier problem

I’m trying to use Transform Applier in VPHOT. I get an error message giving lines from the source code. Can someone help me understand what is wrong?

Hi,

could be a temporary overload of the system, hav you retried after a while?

I just did a transformation and worked as expected.

Open an image. Go back to the image list. Try the transform again.

Ray

Thanks for responding. I’ve tried again this morning with the same result. There is something wrong with my input file. I found an old file for a different star that TA processes with no problem. I’m looking at the report files, but so far, I have not been able to find the difference. The file for Vend 33 works, but the one for GSC 2937-1066 does not.
AAVSO_Report_Vend_33_2024-10-07_data_20250104_b.csv (12.4 KB)
AAVSO_Report_GSC_2937-1066_2025-08-29_for_TA_2.csv (67.7 KB)

Hi,

there is a size limit on the files that the transform applier can manage,

could you try to split the file that is failing in shorter files (max 100 lines)

I tried to process just the first 100 lines, but that didn’t help. I still get the same error message.

Hi,

usually the file size is the culprit but in this case something different is at play.

I tested your file locally locally but I didn’t get the exception so maybe something has to be fixed on the server.

I have asked Geoge Silvis to check the server as I haven’t access to it.

For this VPhot error where it says “TA failed to start..” the workaround that TRE recommended is worth a try:
Go back to the images list and display one of the images. This invokes the same dll that TA needs.
Now go try TA again.
George

You said that you tested my file locally and did not get the exception. Does that mean that you were able to transform the measurements?

George,
I tried opening an image and then going to TA. I still get the same error message.

Well, this is a puzzle.
Same error as before ("T ?A failed 3 times…)?
This error is before TA starts. If you get this error, everyone would be getting it.

I’ve rebooted the server. Maybe that will help.

George

George,
Now I get an error even before VPHOT starts.

503 Service Temporarily Unavailable

I think the problem is with my input file. Over the last few days, when I got to VPHOT, I could run another file for a different star (Vend 33) through TA, and it would process with no trouble. Then I could try the one for GSC 2937-1066, and I would get the error message. I created a shorter file with only the first 100 measurements, and got the same result. I’ve looked at the two files, and except for the star names and magnitude values, they look the same.

OK, I just tried it again. VPHOT started this time. TA will transform this file.
AAVSO_Report_Vend_33_2024-10-07_data_20250104_b.csv (12.4 KB)

I get the error message with this file:

[AAVSO_Report_GSC_2937-1066_2025-08-29_for_TA_2.csv|attachment]
(upload://4i0tcNk4BLuCX5MneiEtmCb4X9I.csv) (67.7 KB)

Allen

George,
I also tried a shorter list and got the same result.

AAVSO_Report_GSC_2937-1066_2025-08-28_short.csv (4.2 KB)

Allen:

Does that star name (GSC_2937-1066) work in VSP? If it is not in VSX, I don’t think it will work in TA?

Edit: Interesting that when I put the name into the “Pick a Star” box on main AAVSO page, it said it was not in VSX BUT when I went to VSX page itself, it did work. Server problem?

Ken

Ken,
VSX will find the star with GSC 2937-1066 as input, but it returns the star name with leading zeros (GSC 02937-01066). I tried adding the leading zeros to the short file, but I still get the error message.

Allen: Try the name (GSC 2937-1066) in ‘Pick a Star’. What do you get?

Ken,
If I enter GSC 2937-1066 and ask for a finder chart, it says that the star is not in VSX, but if I enter GSC 02937-01066 it returns a chart. By the way, I tried using the RA and Dec in place of the star name in the short file, and that didn’t work either.

What format did you use for RA and Dec in short file? Did that specific format work in VSX?

The KNAMEs are too long. limit is 20

You are the first that I know to hit this problem.
For now, just trim the KNAMEs