Missing paleomeasurement values

[sofiakje]

Hi, I have a problem when editing a LiPD file in the playground. When I download the file, the data in the paleomeasurement tables seem to get lost. When opening the file again, I get these errors:

The number of columns are right in the json, but not in the csv files. The columns are still there in the playground, but the values are not. Any ideas on how I can fix this?

Thanks,
Sofia

[nickmckay]

Hmm, it's hard to say. Has this happened more than once? @chrismheiser and @DaveEdge1 , this isn't a known issue, is it?

[DaveEdge1]

I haven't seen this issue before. I just tried uploading a lipd file, deleting a column from a paleodata measurement table, downloading this edited verison, and uploading it. I wasn't able to replicate the error.

Could you provide a simple example of how to reproduce this error?

[sofiakje]

It has happened before, but then I think it was related to using D=mapEnsembleToPaleoData() and writeLipd(D), which made that file difficult to work with in the playground. I haven't done that this time, but I've made a bunch of changes to the file, and can't figure out which one triggered these errors. Here are the edits I can think of:

• Updating some of the Standard fields (e.g., Variable name, Units, Proxy)
• Removing 'Interpretation 1' from Additional fields for some entries (some interpretations I did no longer want in the file, and some didn't have any info in them)
• Adding new columns to the paleomeasurement tables

Sounds like there might be an issue with my file, so I could send it to you if that makes it easier to locate the issue? I've tried to simply re-add the data, but they are lost again when downloading+uploading the edited version.

[DaveEdge1]

Hi Sofia,

Yes, pass the file along (david.edge@nau.edu), and I'd be happy to take a look.

-Dave

[nickmckay]

So, I observed this behavior on the playground today with a couple different files. It wasn't consistent though and sometimes it rendered fine. For me at least, the files were fine, it seemed to be a playground issue.

…

On Fri, May 10, 2024, 5:42 PM Dave Edge ***@***.***> wrote: Hi Sofia, Yes, pass the file along ***@***.***), and I'd be happy to take a look. -Dave — Reply to this email directly, view it on GitHub <#91 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACXPOZ2L2XANA336P37KOMLZBVSOTAVCNFSM6AAAAABHNEKXIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVGQYTCOJZGM> . You are receiving this because you commented.Message ID: ***@***.***>