enable uniqueId strings to be written to centroid file

[jchiang87]

This change supports using strings that are not cast-able as ints for object ids of instance catalog entries.

[cwwalter]

Assuming uniqueId is now a string this looks fine.

[cwwalter]

I guess formatting might not look good if there are other strings in there with very long SN names now.

[cwwalter]

Do you know the maximum length of a SN string yet?

[jchiang87]

Actually, I think the SNe ids will be rather short, e.g., 'MS_587_6'...one of the advantages of allowing non-numeric characters.

[cwwalter]

Will it be added to the end of the uniqueId?

Currently the output looks like this:

SourceID                   Flux       xPix       yPix
470331623428        23781.15037    3824.62    3957.35
1605819826180        2504.62232    3984.03    3737.81
1704279223300        2190.84309    3996.09    3666.65

I was thinking if we knew the length we could up the 1st field width.

[jchiang87]

@danielsf can say more definitively, but from the implementation, I inferred that strings like MS_587_6 will be the entire uniqueId.

[danielsf]

Jim is correct. As implemented now, the entire SN uniqueId is something like [survey name]_[healpix id]_[number within healpix]

[danielsf]

(MS == "main survey")

[cwwalter]

So, no way to tell about the connection to the host galaxy?

[jchiang87]

That info is in the SN db that the instance catalog generation code reads.

[cwwalter]

That info is in the SN db that the instance catalog generation code reads.

Right, I was just wondering if that should be encoded in the uniqueID so you wouldn't need to go back and look at the DB to figure that out. But, if it isn't a important use case for users then it doesn't matter.