CIF_PARSE(1)

🌸 CIF_PARSE πŸ’…

okay bestie, welcome to cif_parse from the General Commands Manual section one β€” she's a lil command-line girly whose whole thing is: you hand her a CIF file, she parses it, and she prints out the structure that the CIF parser built for you. lowkey iconic behaviour tbh πŸŽ€


✨ NAME ✨

cif_parse β€” parse a CIF file and print out the structure generated by the CIF parser. that's it, that's the job πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

cif_parse --options input1.cif input*.cif

🌈 DESCRIPTION 🌈

so basically: parse a CIF file and print out the structure generated by the CIF parser. no cap, that's literally the whole vibe. you feed her CIF, she gives you the parsed structure. periodt ✨


πŸ‘‘ OPTIONS πŸ‘‘

  • --input-cif, --input-json β€” tells her what format your input file(s) are in. the default is CIF, so if you don't say anything she just assumes CIF 🧚
  • --output-dump β€” outputs the parsed CIF file in internal dump format. this is the default, so she does it without you even asking 🫢
  • --output-json β€” outputs the generated structure in JSON instead. for the JSON girlies πŸ’œ
  • --json β€” sets both the input and output formats to JSON. one flag, full JSON commitment, main character energy fr fr πŸ”₯
  • --use-perl-parser β€” uses the Perl parser for CIF parsing 🌸
  • --use-c-parser β€” uses the Perl & C parser for CIF parsing πŸ’…
  • --help, --usage β€” outputs a short usage message (this message!) and exits. she's helping, she's leaving, she's booked and busy 😭
  • --version β€” outputs version information and exits. just the numbers, no small talk ⭐

πŸ’€ REPORTING BUGS πŸ’€

found a bug? not her fault but also please tell her β€” report cif_parse bugs using e-mail: cod-bugs@ibt.lt πŸ™ˆ


and that's the whole page, bestie πŸ’– it's from the General Commands Manual and it lives under the name CIF_PARSE(1) β€” the footer said exactly that, CIF_PARSE(1), with no extra source, version or date to spill, so there's nothing more to report. slay, stay parsed, bye πŸŽ€βœ¨