Skip to content

Conversation

@ddmadsen
Copy link

Read optional PVP fields using the flattened structure (vectorParametersFlatten) similar to the CRSD code. That makes the for-loop a lot simpler. I also moved support for the AddedPVP from the for-loop to the flattened structure.

Note this keeps the PVP data structure to a single layer.

Previous => New
pvp.TxAntenna.TxACX => pvp.TxACX
pvp.TxAntenna.TxACY => pvp.TxACY
pvp.TxAntenna.TxEB=> pvp.TxEB
pvp.RcvAntenna.RcvACX => pvp.RcvACX
...

The new format seemed to be what write_cphd_vbmeta is expecting.

Also some other fixes. I'm pretty sure that xml_meta.PVP.TxPulse.TxAntenna should be xml_meta.PVP.TxAntenna but I don't have any CRSD data to check and the draft standard I have doesn't include TxAntenna at all. This would be correct for CPHD data. Also added code to handle AddedPVP when outputting CPHD (previously caused an error).

… RcvAntenna and TxAntenna similar to AddedPVP which is the format the CPHD writer expects
…a.PVP.TxAntenna but I don't have any CRSD data to check and the draft standard I have doesn't include TxAntenna at all. This would be correct for CPHD data.

Handle AddedPVP when outputting CPHD.
…a.PVP.TxAntenna but I don't have any CRSD data to check and the draft standard I have doesn't include TxAntenna at all. This would be correct for CPHD data.

Handle AddedPVP when outputting CPHD.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant