MarkupsLine .fcsv loads as MarkupsFiducials

[jmhuie (Jonathan Huie)]

@muratmaga

The only time it makes sense to curves as fcsv, if you are using the control points as semi-landmarks in the analysis. Is that your use case?

@lassoan

@jmhuie Can you write a bit more about your application and how do you process exported data (what programming language or software do you use)

I have been using the curves as semi-landmarks and exporting them as .fscv to be read and processed in R. I recognize the issue with .fscv not holding any data and trying to load those back into Slicer.

@muratmaga

@lassoan

They cannot be parsed by standard csv readers because they have an invalid header (multiple lines of non comma-separated values). Do they manually remove the first few lines after each saving? Do they remove those lines programmatically in their analysis scripts?

Reading the coordinates from fcsv into a dataframe in R is a single liner, which they loop over.
read.csv(file='F.fcsv', skip=2, header=T)[,2:4]
that’s what most people do.

I do something along this line. I’ve written a short function in R that reads all of the .fscv files with a “XXXX_Genus_species.fscv” from a folder and converts it into an R friendly format. XXXX could represent any set of MarkupFiducials or curve with semi-landmarks. From there, it’s not really that bad to concatenate curves and points.