takita : the LINENAME field was not fed in your software version, so the content should not be interpreted. It's solved and will be part of the next release. Thank you for having raised it.

Is it a blocking point and do you want a fix for your version ? or could you wait for next release (next week) ? (honestly I prefer last one )

OK, there's no need to rush.  I wait the next release.

Although the new pipeline was not yet working at NAOJ, I have checked the sample output files (pfs_datapack_sp8), and found another problem about 'LINENAME'. This field was defined as "TFORM = 15A", but this was not enough to describe the full line name, like '[OIII] (double-foo)' (see attached image). However, I prefer using short name like 'oiii_4959' which was used in SDSS. Here is what I'm thinking about line names.
linelist = ['abs_h_alpha', 'abs_h_beta', 'abs_h_gamma', 'abs_h_delta', 'neiii_3869', 'h_delta', 'h_gamma', 'h_beta', 'oiii_5007', 'oiii_4959', 'hei_5876', 'oi_6300', 'nii_6548', 'h_alpha', 'nii_6584', 'sii_6717', 'sii_6731', 'ariii7135', 'oii_3729', 'oii_3726', 'civ_1550', 'civ_1548', 'ly_alpha', 'oiii_4363']
Note that wavelengths were selected from SDSS ones.

Ok, I get. Idealy it could be nice to change the line names in the dedicated calibration file, but I expect side effects. So, in short time, I will match simply our line names with SDSS ones at the end of processing ( i.e. writing product)

In the latest pipeline, it looks that the lines are still like this:
['HalphaA' 'HbetaA' 'HgammaA' 'HdeltaA' 'NeIII' 'Hdelta' 'Hgamma' 'Hbeta' '[OIII](doublet-' '[OIII](doublet-' 'HeI5876' '[OI]6301' '[NII](doublet-1' 'Halpha' '[NII](doublet-1' '[SII]6716' '[SII]6731' 'ArIII7136' '[OII]3729' '[OII]3726' 'CIV1550' 'CIV1548' 'LyAE' 'OIII4364']