CIF_EVAL_NUMBERS(1)

πŸ’– CIF_EVAL_NUMBERS β€” the girlies are evaluating numbers πŸ’–

okay so bestie, this is a page from the General Commands Manual (section 1, we love a section 1) and it's about cif_eval_numbers, which is genuinely such a useful little icon. let me put you on. 🫢


✨ NAME ✨

cif_eval_numbers β€” read a CIF file and convert those number values that are written as simple fractions (e.g. "1/4") into a single floating point number.

like. it literally reads your CIF, spots the cute little fraction numbers like "1/4", and turns them into one actual floating point number. that's the whole job. she's focused, she's employed, she's thriving. πŸ’…


🌈 SYNOPSIS 🌈

cif_eval_numbers --options input1.cif input*.cif

so you run it with your options, then one or more CIF files β€” and yes you can absolutely wildcard it with input*.cif, go off. ✨


πŸ¦‹ DESCRIPTION πŸ¦‹

Read a CIF file and convert those number values that are written as simple fractions (e.g. "1/4") into a single floating point number.

that's it, that's the vibe. no cap. πŸŽ€


πŸ’… OPTIONS πŸ’…

  • -d, --dictionary cif_core.dic β€” use the specified DDL1 dictionary for determining which values are numeric. so like, the dictionary is the one deciding who counts as a number around here. gatekeeping, honestly, but valid. πŸ‘‘
  • -t, --tags-to-fix _tag_1,_tag_2,_tag_3 β€” specify an explicit list of tags that should be evaluated as numeric, without relying on a dictionary. no middleman, no committee, just you picking the tags yourself. main character energy fr fr.
  • --fix-syntax-errors β€” try to fix those syntax errors in input CIFs that can be corrected unambiguously. she's a fixer, but only when there's exactly one possible fix. no guessing. πŸ’–
  • --no-fix-syntax-errors, β€” the no-fix option, spelled this way.
  • --dont-fix-syntax-errors β€” do not try to fix syntax errors in input CIFs (default). she leaves the mess exactly as she found it. respectfully. πŸ™ˆ
  • --use-perl-parser β€” use development CIF parser written in Perl.
  • --use-c-parser β€” use faster C/Yacc CIF parser (default). speed. she's fast. πŸ”₯
  • --debug β€” enable debug messages.
  • --no-debug β€” disable debug messages (default).
  • --help, --usage β€” output a short usage message (this message) and exit. our girl is so helpful.
  • --version β€” output version information and exit.

😭 REPORTING BUGS 😭

found a bug? first of all, deep breaths. then report cif_eval_numbers bugs using e-mail:

cod-bugs@ibt.lt

she wants to hear from you. she wants to grow. 🌸


lowkey remember: the two parser flags are a whole vibe check β€” --use-c-parser is the default and it's the fast one, --use-perl-parser is the development one. pick wisely bestie. 🧚

okay so that's the whole page β€” cif_eval_numbers from the General Commands Manual, page CIF_EVAL_NUMBERS(1), and the footer on this one was literally just the title again, CIF_EVAL_NUMBERS(1), same as the header. periodt. go evaluate some numbers. slay. πŸ’œβ­πŸŽ€