I’m exploring an end-to-end flow where a 1550 nm FMCW LiDAR front end in CODE V (5 mm entrance pupil, 0.8 NA receive) feeds a SiN PIC model in Lumerical, and I want the loss, polarization state (Jones), and tolerance budgets to stay consistent across both. Has anyone found a clean handoff for field data and spec budgets — ZOS-API to INTERCONNECT, CODE V + RSoft Link, or something else that survives Monte Carlo?
It’s tricky balancing the data flow between tools like CODE V and Lumerical. I had success using the ZOS-API — just make sure to automate the export of field data to avoid the headache of mismatched parameters later. It’s like trying to sync a band — if everyone doesn’t keep tempo, things get messy fast. @OP, have you looked into using a common data format for easier handoff?
I’ve found that automating the field data transfer really cuts down on errors. It’s like using a conveyor belt instead of carrying each piece manually — way less chance of dropping something! @sjones67, have you considered setting up a script for that?
Getting the polarization state right can be a real headache, especially when switching tools. I once had better luck using the RSoft Link for data handoff since it seemed to keep the specs more aligned across platforms. But it’s definitely a juggling act — just like trying to keep all your ducks in a row while riding a unicycle; @gordon_tate82 might have some thoughts on this too.