ck2yaml(1)

πŸ“¦ version 2.6.0, in epel 9

Okay bestie, welcome to ck2yaml(1) from the General Commands Manual β€” the Chemkin-II-to-Cantera converter that is, honestly, that girl πŸ’…. Manual name? Folded in near the top like a little name tag, and we are obsessed. Now let’s get into it, because this page is lowkey a whole serve. ✨

πŸ’– NAME πŸ’–

ck2yaml β€” convert Chemkin-II-format mechanisms to Cantera YAML input files πŸ¦‹

✨ SYNOPSIS ✨

ck2yaml [--input=<filename>] [--thermo=<filename>]
[--transport=<filename>] [--surface=<filename>] [--name=<name>]
[--extra=<filename>] [--output=<filename>] [--permissive] [--quiet]
[--no-validate] [-d | --debug]

🌸 DESCRIPTION 🌸

So ck2yaml converts a Chemkin-II-format reaction mechanism file to Cantera input format. The resulting Cantera input file contains phase definitions, species definitions, and reaction definitions, depending on the inputs provided. The Cantera-format mechanism is written to the file named by output β€” that’s the output filename situation, bestie, and if you don’t give one, the option below has you covered. πŸ’…

πŸŽ€ The parameters are as follows πŸŽ€

  • --input=<filename> β€” This is the Chemkin-II gas-phase reaction mechanism file to be converted. It contains the declarations of the elements and species, as well as the reactions (if any), and it may also contain the thermodynamic and transport data. One file carrying a lot, honestly main character energy πŸ‘‘.
  • --thermo=<filename> β€” Thermodynamic property database. If the input file does not have a THERMO section, or does not have entries for one or more species, this file will be searched for the required thermo data. Also, a YAML file containing only species definitions (which can be referenced from phase definitions in other input files) can be created by specifying a thermo file with no input file. Cute and useful? We love 🧚.
  • --transport=<filename> β€” Transport property database. If this file name is supplied, transport property parameters will be taken from this file and included in the output Cantera-format file. If this parameter is omitted, and no TRANSPORT section was included in the main input file, no transport property parameters will be included in the output. Facts are facts πŸ’….
  • --surface=<filename> β€” Surface phase definition. If this file name is supplied, an additional phase entry for a surface phase will be read from this file, and a reactions section will be created for any surface reactions defined in this file. Surface reactions made the list ✨.
  • --name=<name> β€” Optional identification string, used to set the name of the ideal-gas phase in the Cantera-format output. If this parameter is omitted, it will be set to gas. Default is gas, no cap πŸ’¨.
  • --extra=<filename> β€” This option takes a YAML file as input. It can be used to add to the file description, or to define custom fields that are included in the YAML output. Custom fields? We love a personalized touch πŸŽ€.
  • --output=<filename> β€” If the output file name is not given, an output file will be created with the same name as the input file, with the extension changed to .yaml. So it’s gonna name itself, bestie πŸ¦‹.
  • --permissive β€” Allows certain recoverable parsing errors (such as duplicate transport data) to be ignored. Recoverable? Ignored? Chill vibes only 😌.
  • --quiet β€” Disables all non-error output, for use in batch processing. Silence, but make it efficient 🀫.
  • --no-validate β€” Disables validation of the converted mechanism by importing it from the Cantera Python module. No-validation era, use responsibly πŸ‘€.
  • -d | --debug β€” Enables additional debugging output. For when you need the tea, and by tea I mean debug info 🍡.

🌈 EXAMPLE 🌈

ck2yaml --input=chem.inp --thermo=therm.dat --transport=tran.dat

mwah πŸ’‹ β€” this iconic page is brought to you by source/version ck2yaml, dated 6 Feb 2021, and yes bestie, it’s still ck2yaml(1) πŸŽ€. Now go convert something iconic. πŸ’–

πŸ“¦ where this page comes from