I noticed this strange name for a CUDA50 WU on my computer. Never seen this before. What is the meaning of the "guppi" and "MESSIER" parts in the file name?

As mentioned in the Breakthough Listen data now flowing announcement, Eric said:

Eric Korpela wrote:

Could someone please explain the information in the new file names on the SSP?

blc3_2bit_guppi_57451_19304_HIP62472_0003

blc3: Breakthrough Listen
2bit: bits per real sample (4 bit per complex sample)
guppi: File format (Greenbank Ultimate Pulsar Processing Instrument)
57451: Modified Julian Date
19304: Seconds past midnight
HIP62472: Object Name
0003: Observation sequence number

Thanks. I also found this thread:
https://setiathome.berkeley.edu/forum_thread.php?id=79477#1781656

Just watched it while the WU was processed. Took 3 seconds only.
<core_client_version>7.6.22</core_client_version>
<![CDATA[
<stderr_txt>
v8 task detected
setiathome_CUDA: Found 1 CUDA device(s):
nVidia Driver Version 359.06
Device 1: GeForce GTX 660 Ti, 2048 MiB, regsPerBlock 65536
computeCap 3.0, multiProcs 7
pciBusID = 1, pciSlotID = 0
In cudaAcc_initializeDevice(): Boinc passed DevPref 1
setiathome_CUDA: CUDA Device 1 specified, checking...
Device 1: GeForce GTX 660 Ti is okay
SETI@home using CUDA accelerated device GeForce GTX 660 Ti
pulsefind: blocks per SM 4 (Fermi or newer default)
pulsefind: periods per launch 100 (default)
Priority of process set to BELOW_NORMAL (default) successfully
Priority of worker thread set successfully

setiathome enhanced x41zi (baseline v8), Cuda 5.00

setiathome_v8 task detected
Detected Autocorrelations as enabled, size 128k elements.
Work Unit Info:
...............
WU true angle range is : 0.307191

GPU current clockRate = 1267 MHz

re-using dev_GaussFitResults array for dev_AutoCorrIn, 4194304 bytes
re-using dev_GaussFitResults+524288x8 array for dev_AutoCorrOut, 4194304 bytes
Thread call stack limit is: 1k
Find triplets Cuda kernel encountered too many triplets, or bins above threshold, reprocessing this PoT on CPU...
cudaAcc_free() called...
cudaAcc_free() running...
cudaAcc_free() PulseFind freed...
cudaAcc_free() Gaussfit freed...
cudaAcc_free() AutoCorrelation freed...
cudaAcc_free() DONE.
Cuda sync'd & freed.
Preemptively acknowledging a safe Exit. ->
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected equals the storage space allocated.

Flopcounter: 204591674.000000

Spike count: 0
Autocorr count: 0
Pulse count: 0
Triplet count: 30
Gaussian count: 0
Worker preemptively acknowledging an overflow exit.->
called boinc_finish
Exit Status: 0
boinc_exit(): requesting safe worker shutdown ->
boinc_exit(): received safe worker shutdown acknowledge ->
Cuda threadsafe ExitProcess() initiated, rval 0

</stderr_txt>
]]>

Curious about where HIP62472 is located?

I use stellarium, free to use, just put HIP62472 in the search window and

it takes you for a ride may have to get rid of the ground and atmosphere.

then use the mouse, scroll to zoom in on the object, which seems to be

a double star HIP62472A and HIP62472B

just a fyi

PS it also works for those Messy names like MESSIER031 although it likes M 31 better

Any triplet scores perhaps?

Checking the logs, I do find a triplet of 24.06 from a WU which had 9 more lines as well in the triplets table in SMV, all having a power or score of 19.87.

But assumedly you are not supposed to associate or relate such a triplet score with being something else.

Here we most likely are still left to be guessing.