Add EC launcher & gyrotron information to ec_data output

added 1 commit

• 3659ccf5 - Add ec_inputs structure to ec_data call, launching write_pgyro

Compare with previous version

added 1 commit

• ae646ee1 - Make launcher num labels for both ec_data and ec_inputs

Compare with previous version

resolved all threads

resolved all threads

added 1 commit

• 8d85672f - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

added 1 commit

• 9fd6a646 - Add check_nodes_filled call to ec_data with toray & cleanup empty outputs

Compare with previous version

added 1 commit

• 22c338f3 - Change again, add try catch and flag to check if data retrieved completely

Compare with previous version

added 1 commit

• 8ce72d21 - Add some checks to identify why ec_data from toray could not be read

Compare with previous version

requested review from @osauter

@osauter can we merge this?

resolved all threads

added 8 commits

• 6db3b452 - 1 commit from branch master
• d8f4007a - add integrated cd and pdens to ec_data output and correct x dim for different launchers
• c790f1eb - Add ec_inputs structure to ec_data call, launching write_pgyro
• cdf5fe11 - Make launcher num labels for both ec_data and ec_inputs
• 29e74f5e - Apply 1 suggestion(s) to 1 file(s)
• 3f99932b - Add check_nodes_filled call to ec_data with toray & cleanup empty outputs
• 33070e9a - Change again, add try catch and flag to check if data retrieved completely
• f1ceba89 - Add some checks to identify why ec_data from toray could not be read

Compare with previous version

Hi @osauter, I just rebased on master, thus again ready to merge. I saw that you resolved all threads 4 weeks ago but don't know if this means I should merge it. Should I? ;) Is it fine from your side?