forked from cclib/cclib.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathdata_notes.html
More file actions
791 lines (700 loc) · 70.6 KB
/
Copy pathdata_notes.html
File metadata and controls
791 lines (700 loc) · 70.6 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
<!DOCTYPE html>
<!--[if IE 8]><html class="no-js lt-ie9" lang="en" > <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en" > <!--<![endif]-->
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Parsed data notes — cclib 1.3.1 documentation</title>
<link rel="stylesheet" href="_static/css/theme.css" type="text/css" />
<link rel="top" title="cclib 1.3.1 documentation" href="index.html"/>
<link rel="next" title="Calculation methods" href="methods.html"/>
<link rel="prev" title="Parsed data (version 1.3.1)" href="data.html"/>
<script src="_static/js/modernizr.min.js"></script>
</head>
<body class="wy-body-for-nav" role="document">
<div class="wy-grid-for-nav">
<nav data-toggle="wy-nav-shift" class="wy-nav-side">
<div class="wy-side-nav-search">
<a href="contents.html" class="icon icon-home"> cclib
</a>
<div role="search">
<form id="rtd-search-form" class="wy-form" action="search.html" method="get">
<input type="text" name="q" placeholder="Search docs" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</div>
</div>
<div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation">
<ul class="current">
<li class="toctree-l1"><a class="reference internal" href="index.html">Overview</a><ul>
<li class="toctree-l2"><a class="reference internal" href="index.html#summary">Summary</a></li>
<li class="toctree-l2"><a class="reference internal" href="index.html#how-to-use-cclib">How to use cclib</a></li>
<li class="toctree-l2"><a class="reference internal" href="index.html#about-cclib">About cclib</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="tutorial.html">Tutorial</a><ul>
<li class="toctree-l2"><a class="reference internal" href="tutorial.html#requirements">Requirements</a></li>
<li class="toctree-l2"><a class="reference internal" href="tutorial.html#debian-gnu-linux-systems">Debian GNU/Linux systems</a></li>
<li class="toctree-l2"><a class="reference internal" href="tutorial.html#manual-download-and-install">Manual download and install</a></li>
<li class="toctree-l2"><a class="reference internal" href="tutorial.html#what-next">What next?</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="data.html">Parsed data (version 1.3.1)</a><ul>
<li class="toctree-l2"><a class="reference internal" href="data.html#description-of-parsed-data">Description of parsed data</a></li>
<li class="toctree-l2"><a class="reference internal" href="data.html#details-of-current-implementation">Details of current implementation</a></li>
</ul>
</li>
<li class="toctree-l1 current"><a class="current reference internal" href="">Parsed data notes</a><ul>
<li class="toctree-l2"><a class="reference internal" href="#aonames">aonames</a></li>
<li class="toctree-l2"><a class="reference internal" href="#aooverlaps">aooverlaps</a></li>
<li class="toctree-l2"><a class="reference internal" href="#atombasis">atombasis</a></li>
<li class="toctree-l2"><a class="reference internal" href="#atomcharges">atomcharges</a></li>
<li class="toctree-l2"><a class="reference internal" href="#atomcoords">atomcoords</a></li>
<li class="toctree-l2"><a class="reference internal" href="#atommasses">atommasses</a></li>
<li class="toctree-l2"><a class="reference internal" href="#atomnos">atomnos</a></li>
<li class="toctree-l2"><a class="reference internal" href="#atomspins">atomspins</a></li>
<li class="toctree-l2"><a class="reference internal" href="#ccenergies">ccenergies</a></li>
<li class="toctree-l2"><a class="reference internal" href="#charge">charge</a></li>
<li class="toctree-l2"><a class="reference internal" href="#coreelectrons">coreelectrons</a></li>
<li class="toctree-l2"><a class="reference internal" href="#etenergies">etenergies</a></li>
<li class="toctree-l2"><a class="reference internal" href="#etoscs">etoscs</a></li>
<li class="toctree-l2"><a class="reference internal" href="#etsecs">etsecs</a></li>
<li class="toctree-l2"><a class="reference internal" href="#etsyms">etsyms</a></li>
<li class="toctree-l2"><a class="reference internal" href="#fonames">fonames</a></li>
<li class="toctree-l2"><a class="reference internal" href="#fooverlaps">fooverlaps</a></li>
<li class="toctree-l2"><a class="reference internal" href="#gbasis">gbasis</a></li>
<li class="toctree-l2"><a class="reference internal" href="#geotargets">geotargets</a></li>
<li class="toctree-l2"><a class="reference internal" href="#geovalues">geovalues</a></li>
<li class="toctree-l2"><a class="reference internal" href="#hessian">hessian</a></li>
<li class="toctree-l2"><a class="reference internal" href="#homos">homos</a></li>
<li class="toctree-l2"><a class="reference internal" href="#mocoeffs">mocoeffs</a></li>
<li class="toctree-l2"><a class="reference internal" href="#moenergies">moenergies</a></li>
<li class="toctree-l2"><a class="reference internal" href="#moments">moments</a></li>
<li class="toctree-l2"><a class="reference internal" href="#mosyms">mosyms</a></li>
<li class="toctree-l2"><a class="reference internal" href="#mpenergies">mpenergies</a></li>
<li class="toctree-l2"><a class="reference internal" href="#mult">mult</a></li>
<li class="toctree-l2"><a class="reference internal" href="#natom">natom</a></li>
<li class="toctree-l2"><a class="reference internal" href="#nbasis">nbasis</a></li>
<li class="toctree-l2"><a class="reference internal" href="#nmo">nmo</a></li>
<li class="toctree-l2"><a class="reference internal" href="#optdone">optdone</a></li>
<li class="toctree-l2"><a class="reference internal" href="#scfenergies">scfenergies</a></li>
<li class="toctree-l2"><a class="reference internal" href="#scftargets">scftargets</a></li>
<li class="toctree-l2"><a class="reference internal" href="#scfvalues">scfvalues</a></li>
<li class="toctree-l2"><a class="reference internal" href="#vibdisps">vibdisps</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="methods.html">Calculation methods</a><ul>
<li class="toctree-l2"><a class="reference internal" href="methods.html#c-squared-population-analysis-cspa">C squared population analysis (CSPA)</a><ul>
<li class="toctree-l3"><a class="reference internal" href="methods.html#custom-fragments">Custom fragments</a></li>
<li class="toctree-l3"><a class="reference internal" href="methods.html#custom-progress">Custom progress</a></li>
</ul>
</li>
<li class="toctree-l2"><a class="reference internal" href="methods.html#mulliken-population-analysis-mpa">Mulliken population analysis (MPA)</a><ul>
<li class="toctree-l3"><a class="reference internal" href="methods.html#id1">Custom fragments</a></li>
<li class="toctree-l3"><a class="reference internal" href="methods.html#id2">Custom progress</a></li>
</ul>
</li>
<li class="toctree-l2"><a class="reference internal" href="methods.html#lowdin-population-analysis">Löwdin Population Analysis</a></li>
<li class="toctree-l2"><a class="reference internal" href="methods.html#overlap-population-analysis">Overlap Population Analysis</a></li>
<li class="toctree-l2"><a class="reference internal" href="methods.html#density-matrix-calculation">Density Matrix calculation</a></li>
<li class="toctree-l2"><a class="reference internal" href="methods.html#mayer-s-bond-orders">Mayer’s Bond Orders</a></li>
<li class="toctree-l2"><a class="reference internal" href="methods.html#charge-decomposition-analysis">Charge Decomposition Analysis</a><ul>
<li class="toctree-l3"><a class="reference internal" href="methods.html#notes">Notes</a></li>
</ul>
</li>
<li class="toctree-l2"><a class="reference internal" href="methods.html#electron-density-calculation">Electron Density Calculation</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="development.html">Development</a><ul>
<li class="toctree-l2"><a class="reference internal" href="development.html#basic-instructions">Basic instructions</a><ul>
<li class="toctree-l3"><a class="reference internal" href="development.html#cloning-cclib-from-github">Cloning cclib from GitHub</a></li>
<li class="toctree-l3"><a class="reference internal" href="development.html#guidelines">Guidelines</a></li>
<li class="toctree-l3"><a class="reference internal" href="development.html#releasing-a-new-version">Releasing a new version</a></li>
</ul>
</li>
<li class="toctree-l2"><a class="reference internal" href="development.html#testing">Testing</a><ul>
<li class="toctree-l3"><a class="reference internal" href="development.html#unit-tests">Unit tests</a></li>
<li class="toctree-l3"><a class="reference internal" href="development.html#regression-tests">Regression tests</a></li>
<li class="toctree-l3"><a class="reference internal" href="development.html#doctests">Doctests</a></li>
</ul>
</li>
<li class="toctree-l2"><a class="reference internal" href="development.html#websites-related-to-cclib">Websites related to cclib</a></li>
<li class="toctree-l2"><a class="reference internal" href="development.html#developers">Developers</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="data_dev.html">Development parsed data</a><ul>
<li class="toctree-l2"><a class="reference internal" href="data_dev.html#description-of-parsed-data">Description of parsed data</a></li>
<li class="toctree-l2"><a class="reference internal" href="data_dev.html#details-of-current-implementation">Details of current implementation</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="changelog.html">Changelog</a><ul>
<li class="toctree-l2"><a class="reference internal" href="changelog.html#changes-since-cclib-1-3">Changes since cclib-1.3</a></li>
<li class="toctree-l2"><a class="reference internal" href="changelog.html#changes-since-cclib-1-2">Changes since cclib-1.2</a></li>
<li class="toctree-l2"><a class="reference internal" href="changelog.html#changes-since-cclib-1-1">Changes since cclib-1.1</a></li>
<li class="toctree-l2"><a class="reference internal" href="changelog.html#changes-since-cclib-1-0-1">Changes since cclib-1.0.1</a></li>
<li class="toctree-l2"><a class="reference internal" href="changelog.html#changes-since-cclib-1-0">Changes since cclib-1.0</a></li>
<li class="toctree-l2"><a class="reference internal" href="changelog.html#changes-since-cclib-0-9">Changes since cclib-0.9</a></li>
<li class="toctree-l2"><a class="reference internal" href="changelog.html#changes-since-cclib-0-8">Changes since cclib-0.8</a></li>
<li class="toctree-l2"><a class="reference internal" href="changelog.html#changes-since-cclib-0-7">Changes since cclib-0.7</a></li>
<li class="toctree-l2"><a class="reference internal" href="changelog.html#changes-since-cclib-0-6-1">Changes since cclib-0.6.1</a></li>
<li class="toctree-l2"><a class="reference internal" href="changelog.html#changes-since-cclib-0-6-0">Changes since cclib-0.6.0</a></li>
<li class="toctree-l2"><a class="reference internal" href="changelog.html#changes-since-cclib-0-6b">Changes since cclib-0.6b</a></li>
<li class="toctree-l2"><a class="reference internal" href="changelog.html#changes-since-cclib-0-5">Changes since cclib-0.5</a></li>
<li class="toctree-l2"><a class="reference internal" href="changelog.html#changes-since-cclib-0-5b">Changes since cclib-0.5b</a></li>
</ul>
</li>
</ul>
</div>
</nav>
<section data-toggle="wy-nav-shift" class="wy-nav-content-wrap">
<nav class="wy-nav-top" role="navigation" aria-label="top navigation">
<i data-toggle="wy-nav-top" class="fa fa-bars"></i>
<a href="contents.html">cclib</a>
</nav>
<div class="wy-nav-content">
<div class="rst-content">
<div role="navigation" aria-label="breadcrumbs navigation">
<ul class="wy-breadcrumbs">
<li><a href="contents.html">Docs</a> »</li>
<li>Parsed data notes</li>
<li class="wy-breadcrumbs-aside">
<a href="https://github.com/cclib/cclib.github.io/blob/master/sphinx/data_notes.rst" class="fa fa-github"> Edit on GitHub</a>
</li>
</ul>
<hr/>
</div>
<div role="main" class="document">
<div class="section" id="parsed-data-notes">
<span id="index-0"></span><h1>Parsed data notes<a class="headerlink" href="#parsed-data-notes" title="Permalink to this headline">¶</a></h1>
<p>This is a list of descriptions and notes for all the data attributes currently parsed by cclib, either in the official release (1.3.1) or development branch. In particular, this page contains technical details about the interpretation of attributes, how to produce them in the various programs and examples in some cases. For a summary and details of the current implementation by the different parsers, please see the <a class="reference external" href="data.html">extracted data</a> page and its <a class="reference external" href="data_dev.html">development</a> version.</p>
<div class="section" id="aonames">
<h2>aonames<a class="headerlink" href="#aonames" title="Permalink to this headline">¶</a></h2>
<p>This attribute contains the atomic orbital names. These are not normalised as the following examples show, although a reasonable attempt is made to get them close to each other. Users will need to know what each orbital is by knowing the basis set inside out, rather than relying on this data. Such is life, as GAMESS does not provide enough information.</p>
<ul class="simple">
<li>Gaussian gives names of the form: [‘C1_1S’, ‘C1_2S’, ‘C1_2PX’, ‘C1_2PY’, ‘C1_2PZ’, ‘C2_1S’, ‘C2_2S’, ‘C2_2PX’, ‘C2_2PY’, ‘C2_2PZ’, ‘C3_1S’, ‘C3_2S’, ‘C3_2PX’, ‘C3_2PY’, ‘C3_2PZ’, ‘C4_1S’, ‘C4_2S’, ‘C4_2PX’, ‘C4_2PY’, ‘C4_2PZ’, ‘C5_1S’, ‘C5_2S’, ‘C5_2PX’, ‘C5_2PY’, ‘C5_2PZ’, ‘H6_1S’, ‘H7_1S’, ‘H8_1S’, ‘C9_1S’, ‘C9_2S’, ‘C9_2PX’, ‘C9_2PY’, ‘C9_2PZ’, ‘C10_1S’, ‘C10_2S’, ‘C10_2PX’, ‘C10_2PY’, ‘C10_2PZ’, ‘H11_1S’, ‘H12_1S’, ‘H13_1S’, ‘C14_1S’, ‘C14_2S’, ‘C14_2PX’, ‘C14_2PY’, ‘C14_2PZ’, ‘H15_1S’, ‘C16_1S’, ‘C16_2S’, ‘C16_2PX’, ‘C16_2PY’, ‘C16_2PZ’, ‘H17_1S’, ‘H18_1S’, ‘C19_1S’, ‘C19_2S’, ‘C19_2PX’, ‘C19_2PY’, ‘C19_2PZ’, ‘H20_1S’]</li>
<li>GAMESS gives names of the form: [‘C1_1S’, ‘C1_2S’, ‘C1_3X’, ‘C1_3Y’, ‘C1_3Z’, ‘C2_1S’, ‘C2_2S’, ‘C2_3X’, ‘C2_3Y’, ‘C2_3Z’, ‘C3_1S’, ‘C3_2S’, ‘C3_3X’, ‘C3_3Y’, ‘C3_3Z’, ‘C4_1S’, ‘C4_2S’, ‘C4_3X’, ‘C4_3Y’, ‘C4_3Z’, ‘C5_1S’, ‘C5_2S’, ‘C5_3X’, ‘C5_3Y’, ‘C5_3Z’, ‘C6_1S’, ‘C6_2S’, ‘C6_3X’, ‘C6_3Y’, ‘C6_3Z’, ‘H7_1S’, ‘H8_1S’, ‘H9_1S’, ‘H10_1S’, ‘C11_1S’, ‘C11_2S’, ‘C11_3X’, ‘C11_3Y’, ‘C11_3Z’, ‘C12_1S’, ‘C12_2S’, ‘C12_3X’, ‘C12_3Y’, ‘C12_3Z’, ‘H13_1S’, ‘H14_1S’, ‘C15_1S’, ‘C15_2S’, ‘C15_3X’, ‘C15_3Y’, ‘C15_3Z’, ‘C16_1S’, ‘C16_2S’, ‘C16_3X’, ‘C16_3Y’, ‘C16_3Z’, ‘H17_1S’, ‘H18_1S’, ‘H19_1S’, ‘H20_1S’]</li>
</ul>
<p>And for a large basis set calculation on a single C atom...:</p>
<ul class="simple">
<li>Gaussian: [‘C1_1S’, ‘C1_2S’, ‘C1_3S’, ‘C1_4S’, ‘C1_5S’, ‘C1_6PX’, ‘C1_6PY’, ‘C1_6PZ’, ‘C1_7PX’, ‘C1_7PY’, ‘C1_7PZ’, ‘C1_8PX’, ‘C1_8PY’, ‘C1_8PZ’, ‘C1_9PX’, ‘C1_9PY’, ‘C1_9PZ’, ‘C1_10D 0’, ‘C1_10D+1’, ‘C1_10D-1’, ‘C1_10D+2’, ‘C1_10D-2’, ‘C1_11D 0’, ‘C1_11D+1’, ‘C1_11D-1’, ‘C1_11D+2’, ‘C1_11D-2’, ‘C1_12D 0’, ‘C1_12D+1’, ‘C1_12D-1’, ‘C1_12D+2’, ‘C1_12D-2’, ‘C1_13F 0’, ‘C1_13F+1’, ‘C1_13F-1’, ‘C1_13F+2’, ‘C1_13F-2’, ‘C1_13F+3’, ‘C1_13F-3’, ‘C1_14F 0’, ‘C1_14F+1’, ‘C1_14F-1’, ‘C1_14F+2’, ‘C1_14F-2’, ‘C1_14F+3’, ‘C1_14F-3’, ‘C1_15G 0’, ‘C1_15G+1’, ‘C1_15G-1’, ‘C1_15G+2’, ‘C1_15G-2’, ‘C1_15G+3’, ‘C1_15G-3’, ‘C1_15G+4’, ‘C1_15G-4’, ‘C1_16S’, ‘C1_17PX’, ‘C1_17PY’, ‘C1_17PZ’, ‘C1_18D 0’, ‘C1_18D+1’, ‘C1_18D-1’, ‘C1_18D+2’, ‘C1_18D-2’, ‘C1_19F 0’, ‘C1_19F+1’, ‘C1_19F-1’, ‘C1_19F+2’, ‘C1_19F-2’, ‘C1_19F+3’, ‘C1_19F-3’, ‘C1_20G 0’, ‘C1_20G+1’, ‘C1_20G-1’, ‘C1_20G+2’, ‘C1_20G-2’, ‘C1_20G+3’, ‘C1_20G-3’, ‘C1_20G+4’, ‘C1_20G-4’]</li>
<li>GAMESS: [‘C1_1S’, ‘C1_2S’, ‘C1_3S’, ‘C1_4S’, ‘C1_5S’, ‘C1_6X’, ‘C1_6Y’, ‘C1_6Z’, ‘C1_7X’, ‘C1_7Y’, ‘C1_7Z’, ‘C1_8X’, ‘C1_8Y’, ‘C1_8Z’, ‘C1_9X’, ‘C1_9Y’, ‘C1_9Z’, ‘C1_10XX’, ‘C1_10YY’, ‘C1_10ZZ’, ‘C1_10XY’, ‘C1_10XZ’, ‘C1_10YZ’, ‘C1_11XX’, ‘C1_11YY’, ‘C1_11ZZ’, ‘C1_11XY’, ‘C1_11XZ’, ‘C1_11YZ’, ‘C1_12XX’, ‘C1_12YY’, ‘C1_12ZZ’, ‘C1_12XY’, ‘C1_12XZ’, ‘C1_12YZ’, ‘C1_13XXX’, ‘C1_13YYY’, ‘C1_13ZZZ’, ‘C1_13XXY’,’C1_13XXZ’, ‘C1_13YYX’, ‘C1_13YYZ’, ‘C1_13ZZX’, ‘C1_13ZZY’, ‘C1_13XYZ’, ‘C1_14XXX’, ‘C1_14YYY’, ‘C1_14ZZZ’, ‘C1_14XXY’, ‘C1_14XXZ’, ‘C1_14YYX’, ‘C1_14YYZ’, ‘C1_14ZZX’, ‘C1_14ZZY’, ‘C1_14XYZ’, ‘C1_15XXXX’, ‘C1_15YYYY’, ‘C1_15ZZZZ’, ‘C1_15XXXY’, ‘C1_15XXXZ’, ‘C1_15YYYX’, ‘C1_15YYYZ’, ‘C1_15ZZZX’, ‘C1_15ZZZY’, ‘C1_15XXYY’, ‘C1_15XXZZ’, ‘C1_15YYZZ’, ‘C1_15XXYZ’, ‘C1_15YYXZ’, ‘C1_15ZZXY’, ‘C1_16S’, ‘C1_17S’, ‘C1_18S’, ‘C1_19X’, ‘C1_19Y’, ‘C1_19Z’, ‘C1_20X’, ‘C1_20Y’, ‘C1_20Z’, ‘C1_21X’, ‘C1_21Y’, ‘C1_21Z’, ‘C1_22XX’, ‘C1_22YY’, ‘C1_22ZZ’, ‘C1_22XY’, ‘C1_22XZ’, ‘C1_22YZ’, ‘C1_23XX’, ‘C1_23YY’, ‘C1_23ZZ’, ‘C1_23XY’, ‘C1_23XZ’, ‘C1_23YZ’, ‘C1_24XXX’, ‘C1_24YYY’, ‘C1_24ZZZ’, ‘C1_24XXY’, ‘C1_24XXZ’, ‘C1_24YYX’, ‘C1_24YYZ’, ‘C1_24ZZX’, ‘C1_24ZZY’, ‘C1_24XYZ’, ‘C1_25S’, ‘C1_26X’, ‘C1_26Y’, ‘C1_26Z’, ‘C1_27XX’, ‘C1_27YY’, ‘C1_27ZZ’, ‘C1_27XY’, ‘C1_27XZ’, ‘C1_27YZ’, ‘C1_28XXX’, ‘C1_28YYY’, ‘C1_28ZZZ’, ‘C1_28XXY’, ‘C1_28XXZ’, ‘C1_28YYX’, ‘C1_28YYZ’, ‘C1_28ZZX’, ‘C1_28ZZY’, ‘C1_28XYZ’, ‘C1_29XXXX’, ‘C1_29YYYY’, ‘C1_29ZZZZ’, ‘C1_29XXXY’, ‘C1_29XXXZ’, ‘C1_29YYYX’, ‘C1_29YYYZ’, ‘C1_29ZZZX’, ‘C1_29ZZZY’, ‘C1_29XXYY’, ‘C1_29XXZZ’, ‘C1_29YYZZ’, ‘C1_29XXYZ’, ‘C1_29YYXZ’, ‘C1_29ZZXY’]</li>
</ul>
</div>
<div class="section" id="aooverlaps">
<h2>aooverlaps<a class="headerlink" href="#aooverlaps" title="Permalink to this headline">¶</a></h2>
<p>This is a 2-dimensional array which holds the numerical values of the overlap between basis functions (also called atomic orbitals). It is needed for most analyses like <a class="reference external" href="methods.html#mulliken-population-analysis-mpa">Mulliken</a>, <a class="reference external" href="methods.html#c-squared-population-analysis-cspa">C squared</a>, and <a class="reference external" href="methods.html#mayer-s-bond-orders">Mayer’s Bond Orders</a>. The indices of the matrix correspond to the basis functions of interest. This matrix is symmetric, so <tt class="docutils literal"><span class="pre">aooverlaps[i,j]</span></tt> is the same as <tt class="docutils literal"><span class="pre">aooverlaps[j,i]</span></tt>.</p>
<p>Some examples:</p>
<ul class="simple">
<li><tt class="docutils literal"><span class="pre">aooverlaps[0,3]</span></tt> is the overlap between the 1st and 4th basis function</li>
<li><tt class="docutils literal"><span class="pre">aooverlaps[2,:]</span></tt> is a 1-dimensional array containing the overlap between every basis function and the 3rd basis function</li>
</ul>
<p><strong>ADF</strong>: not present by default, printed when <cite>PRINT Smat</cite> is in the input; do not mistake with <a class="reference internal" href="#fooverlaps">fooverlaps</a></p>
<p><strong>DALTON</strong>: no option to print as of version 2013</p>
<p><strong>Gaussian</strong>: iop(3/33=1) must be specified in the input file</p>
</div>
<div class="section" id="atombasis">
<h2>atombasis<a class="headerlink" href="#atombasis" title="Permalink to this headline">¶</a></h2>
<p>The attribute <tt class="docutils literal"><span class="pre">atombasis</span></tt> is a list, each element being a list that contains the atomic orbital indices on the respective atom. For example, <tt class="docutils literal"><span class="pre">atombasis[1]</span></tt> will contain the indices of atomic orbitals on the second atom of the molecule.</p>
</div>
<div class="section" id="atomcharges">
<span id="index-1"></span><h2>atomcharges<a class="headerlink" href="#atomcharges" title="Permalink to this headline">¶</a></h2>
<p>The attribute <tt class="docutils literal"><span class="pre">atomcharges</span></tt> contains the atomic partial charges as taken from the output file. Since these charges are arbitrary and depend on the details of a population analysis, this attribute is dictionary containing any number of various atomic charges. The keys in this dictionary are strings naming the population analysis, and the values are arrays of rank 1 and contain the actual charges.</p>
<p>Currently, cclib parses Mulliken, Löwdin and NPA charges, whose respective dictionary keys are <tt class="docutils literal"><span class="pre">mulliken</span></tt>, <tt class="docutils literal"><span class="pre">lowdin</span></tt> and <tt class="docutils literal"><span class="pre">natural</span></tt>.</p>
<p>Note that in practice these may differ somewhat from the values cclib calculates in the various calculation methods.</p>
<p><strong>Molpro</strong>: use the <tt class="docutils literal"><span class="pre">pop</span></tt> command (see <a class="reference external" href="http://www.molpro.net/info/2010.1/doc/manual/node450.html">http://www.molpro.net/info/2010.1/doc/manual/node450.html</a>)</p>
</div>
<div class="section" id="atomcoords">
<h2>atomcoords<a class="headerlink" href="#atomcoords" title="Permalink to this headline">¶</a></h2>
<p>The attribute <tt class="docutils literal"><span class="pre">atomcoords</span></tt> contains the atomic coordinates as taken from the output file. This is an array of rank 3, with a shape (n,m,3) where n is 1 for a single point calculation and >=1 for a geometry optimisation and m is the number of atoms.</p>
<p><strong>Gaussian</strong>: for geometry optimisations, the “Standard orientation” sections are extracted.</p>
<p><strong>Molpro</strong>: typically prints output about geometry optimisation in a separate logfile. So, both that and the initial output need to be passed to the cclib parser.</p>
</div>
<div class="section" id="atommasses">
<h2>atommasses<a class="headerlink" href="#atommasses" title="Permalink to this headline">¶</a></h2>
<p>The attribute <tt class="docutils literal"><span class="pre">atommasses</span></tt> contains the masses of all atoms in unified atomic mass units, or Daltons (Da). This is an array or rank 1.</p>
</div>
<div class="section" id="atomnos">
<h2>atomnos<a class="headerlink" href="#atomnos" title="Permalink to this headline">¶</a></h2>
<p>An array of integers for the atomic numbers, or the number of protons in the atom nuclei.</p>
</div>
<div class="section" id="atomspins">
<h2>atomspins<a class="headerlink" href="#atomspins" title="Permalink to this headline">¶</a></h2>
<p>The attribute <tt class="docutils literal"><span class="pre">atomspins</span></tt> contains the atomic spin densities as calculated in a population analysis and taken from the output file. Since these densities are arbitrary and depend on the particular population analysis, this attribute is dictionary. In analogy to <a class="reference internal" href="#atomcharges">atomcharges</a>, the keys in this dictionary are strings naming the population analysis, and the values are arrays of rank 1 and contain the actual spin densities.</p>
<p>Currently, cclib parses Mulliken and Löwdin spin densities, whose respective dictionary keys are <tt class="docutils literal"><span class="pre">mulliken</span></tt> and <tt class="docutils literal"><span class="pre">lowdin</span></tt>.</p>
</div>
<div class="section" id="ccenergies">
<span id="index-2"></span><h2>ccenergies<a class="headerlink" href="#ccenergies" title="Permalink to this headline">¶</a></h2>
<p>A one-dimensional array holds the total molecule energies including Coupled Cluster corrections. The array’s length is 1 for single point calculations and larger for optimisations. Only the highest theory level is parsed into this attribute (for example, CCSD energies as opposed to CCD energies, or CCSD(T) as opposed to CCSD energies).</p>
</div>
<div class="section" id="charge">
<h2>charge<a class="headerlink" href="#charge" title="Permalink to this headline">¶</a></h2>
<p>Net charge of the calculated system, in units of <tt class="docutils literal"><span class="pre">e</span></tt>.</p>
</div>
<div class="section" id="coreelectrons">
<h2>coreelectrons<a class="headerlink" href="#coreelectrons" title="Permalink to this headline">¶</a></h2>
<p>The attribute <tt class="docutils literal"><span class="pre">coreelectrons</span></tt> contains the number of core electrons in each atom’s pseudopotentials. It is an array of rank 1, with as many integer elements as there are atoms.</p>
</div>
<div class="section" id="etenergies">
<h2>etenergies<a class="headerlink" href="#etenergies" title="Permalink to this headline">¶</a></h2>
<p>This is a rank 1 array that contains the energies of electronic transitions from a reference state to the excited states of the molecule, in <tt class="docutils literal"><span class="pre">cm<sup>-1</sup></span></tt>. There should be as many elements to this array as there are excited states calculated. Any type of excited state calculation should provide output that can be parsed into this attribute.</p>
<p>Availability:</p>
<ul class="simple">
<li>Configuration Interaction (CIS): Gaussian</li>
<li>Time-dependent DFT (TD-DFT): Gaussian</li>
<li>Time-dependent Hartree-Fock (TD-HF): Gaussian</li>
</ul>
<p>Availability (development version):</p>
<ul class="simple">
<li>Configuration Interaction (CIS): Gaussian, GAMESS, Jaguar</li>
<li>Time-dependent DFT (TD-DFT): Gaussian</li>
<li>Time-dependent Hartree-Fock (TD-HF): Gaussian</li>
</ul>
</div>
<div class="section" id="etoscs">
<h2>etoscs<a class="headerlink" href="#etoscs" title="Permalink to this headline">¶</a></h2>
<p>The attribute <tt class="docutils literal"><span class="pre">etoscs</span></tt> is a rank 1 array that contains the oscillator strengths of transitions from the reference (ground) state to the excited electronic states of the of the molecule. As for <a class="reference internal" href="#etenergies">etenergies</a> and other attributes related to excited states, there should as many elements in this array as there are excited states in the calculation.</p>
<p>Availability:</p>
<ul class="simple">
<li>Configuration Interaction (CIS): Gaussian</li>
<li>Time-dependent DFT (TD-DFT): Gaussian</li>
<li>Time-dependent Hartree-Fock (TD-HF): Gaussian</li>
</ul>
<p>Availability (development version):</p>
<ul class="simple">
<li>Configuration Interaction (CIS): GAMESS, Gaussian, Jaguar</li>
<li>Time-dependent DFT (TD-DFT): Gaussian</li>
<li>Time-dependent Hartree-Fock (TD-HF): Gaussian</li>
</ul>
</div>
<div class="section" id="etsecs">
<h2>etsecs<a class="headerlink" href="#etsecs" title="Permalink to this headline">¶</a></h2>
<p>The singly-excited configurations that contribute to electronic transitions are stored in <tt class="docutils literal"><span class="pre">etsecs</span></tt>. It is a list (for each electronic transition from the reference ground state) of lists (for each singly-excited configuration) with three members each:</p>
<blockquote>
<div><ul class="simple">
<li>a tuple (moindex, alpha/beta), which indicates the MO where the transition begins</li>
<li>a tuple (moindex, alpha/beta), which indicates the MO where the transition ends</li>
<li>a float (which can be negative), the coefficient of this singly-excited configuration</li>
</ul>
</div></blockquote>
<p>In these tuples, the value of alpha/beta is 0 or 1, respectively. For a restricted calculation, this value is always 0, although some programs (GAMESS) sometimes print coefficients for both alpha and beta electrons.</p>
<p>The excitation coefficient is always converted to its unnormalized value by cclib - so the sum of the squared coefficients of all alpha and beta excitations should be unity. It is important to keep in mind, however, that only the square of the excitation coefficient has a physical meaning, and its sign depends on the numerical procedures used by each program.</p>
<p>Availability:</p>
<ul class="simple">
<li>Configuration Interaction (CIS): Gaussian</li>
<li>Time-dependent DFT (TD-DFT): Gaussian</li>
<li>Time-dependent Hartree-Fock (TD-HF): Gaussian</li>
</ul>
<p>Availability (development version):</p>
<ul class="simple">
<li>Configuration Interaction (CIS): GAMESS, Gaussian, Jaguar</li>
<li>Time-dependent DFT (TD-DFT): GAMESS, Gaussian</li>
<li>Time-dependent Hartree-Fock (TD-HF): Gaussian</li>
</ul>
</div>
<div class="section" id="etsyms">
<h2>etsyms<a class="headerlink" href="#etsyms" title="Permalink to this headline">¶</a></h2>
<p>The attributes <tt class="docutils literal"><span class="pre">etsyms</span></tt> is a list containing the symmetries (strings) of the excited states found in the calculation. As for <a class="reference internal" href="#etenergies">etenergies</a> and other attributes related to excited states, there should be as many elements in this list as there are excited states in the calculation.</p>
<p>Note that while the symmetry descriptions start with the string <tt class="docutils literal"><span class="pre">Singlet</span></tt> or <tt class="docutils literal"><span class="pre">Triplet</span></tt>, the exact format differs between programs.</p>
<p>Availability:</p>
<ul class="simple">
<li>Configuration Interaction (CIS): Gaussian</li>
<li>Time-dependent DFT (TD-DFT): Gaussian</li>
<li>Time-dependent Hartree-Fock (TD-HF): Gaussian</li>
</ul>
<p>Availability:</p>
<ul class="simple">
<li>Configuration Interaction (CIS): GAMESS, Gaussian, Jaguar</li>
<li>Time-dependent DFT (TD-DFT): Gaussian</li>
<li>Time-dependent Hartree-Fock (TD-HF): Gaussian</li>
</ul>
</div>
<div class="section" id="fonames">
<h2>fonames<a class="headerlink" href="#fonames" title="Permalink to this headline">¶</a></h2>
<p>ADF uses symmetry-adapted fragment orbitals (SFOs) as its basis. These SFOs are generally orthonormal linear combinations of atomic orbitals. This makes it difficult to determine which individual atomic orbitals form the basis in calculations that have any symmetry. In addition, ADF allows “fragment” calculations which use the molecular orbitals of the fragments (FOs, or fragment orbitals) for building up the calculated molecular orbitals.</p>
<p>The difficulty in handling the basis for a molecule with symmetry and the availability of extra information in the fragment calculations makes using <a class="reference internal" href="#aonames">aonames</a> (as specified for the other formats) inappropriate, except for certain circumstances. Therefore, an extra member called fonames is available for the adfparser.</p>
<p>Some examples:</p>
<p><tt class="docutils literal"><span class="pre">C1+C4_1S+1S</span></tt> - Orbitals from carbon 1 and carbon 4 can interact, and their <tt class="docutils literal"><span class="pre">1S</span></tt> orbitals mix in a positive manner</p>
<p><tt class="docutils literal"><span class="pre">C1+C4_1Px-1Px</span></tt> - Orbitals from carbon 1 and carbon 4 can interact, and their <tt class="docutils literal"><span class="pre">1Px</span></tt> orbitals mix in a negative manner</p>
<p><tt class="docutils literal"><span class="pre">bdt1_37A</span></tt> - Molecular orbital 37A from the fragment bdt1</p>
<p><strong>ADF</strong>: There are no required inputfile options for fonames to be supported; however, if one wishes to have SFOs map directly to atomic basis functions, there are two requirements. First, the <tt class="docutils literal"><span class="pre">Symmetry</span> <span class="pre">NOSYM</span></tt> option must be given to force ADF to not linearly combine atomic orbitals into SFOs. Second, fragment calculations cannot be done (for obvious reasons). Also, it is suggested that <tt class="docutils literal"><span class="pre">Eigval</span> <span class="pre">99999</span> <span class="pre">99999</span></tt> be put into an <tt class="docutils literal"><span class="pre">Eprint</span></tt> block of the input file of a spin-restricted calculation so that every molecular orbital energy will be printed.</p>
</div>
<div class="section" id="fooverlaps">
<h2>fooverlaps<a class="headerlink" href="#fooverlaps" title="Permalink to this headline">¶</a></h2>
<p>This is a 2-dimensional array that holds numerical values for the spacial overlap between basis functions. It is very similar to <a class="reference internal" href="#aooverlaps">aooverlaps</a>, but differs because of the way ADF performs the calculation (see below for more details). The matrix indices correspond to the fragment orbitals; see the examples listed for <a class="reference internal" href="#aonames">aonames</a>.</p>
<p><strong>Background</strong></p>
<p>ADF uses symmetry-adapted fragment orbitals (SFOs) as its basis. These SFOs are generally orthonormal linear combinations of atomic orbitals. This makes it difficult to determine which individual atomic orbitals form the basis in calculations that have any symmetry. In addition, ADF allows “fragment” calculations which use the molecular orbitals of the fragments (FOs, or fragment orbitals) for building up the calculated molecular orbitals.</p>
<p>The difficulty in handling the basis for a molecule with symmetry and the availability of extra information in the fragment calculations makes using aooverlaps (as specified for the other formats) inappropriate, except for certain circumstances. Therefore, an extra member called fooverlaps is available for the ADF parser.</p>
<p><strong>ADF</strong>: There are no required inputfile options for fooverlaps to be supported; however, if one wishes to have SFOs map directly to atomic basis functions, there are two requirements. First, the <tt class="docutils literal"><span class="pre">Symmetry</span> <span class="pre">NOSYM</span></tt> option must be given to force ADF to not linearly combine atomic orbitals into SFOs. Second, fragment calculations cannot be done (for obvious reasons). Also, it is suggested that <tt class="docutils literal"><span class="pre">Eigval</span> <span class="pre">99999</span> <span class="pre">99999</span></tt> be put into an <tt class="docutils literal"><span class="pre">Eprint</span></tt> block of the input file of a spin-restricted calculation so that every molecular orbital energy will be printed.</p>
</div>
<div class="section" id="gbasis">
<span id="index-3"></span><h2>gbasis<a class="headerlink" href="#gbasis" title="Permalink to this headline">¶</a></h2>
<p>This attribute stores information about the Gaussian basis functions that were used in the calculation, per atom using the same conventions as [<a class="reference external" href="http://pyquante.sf.net">http://pyquante.sf.net</a> PyQuante]. Specifically, <tt class="docutils literal"><span class="pre">gbasis</span></tt> is a list of lists iterating over atoms and Gaussian basis functions. The elements (basis functions) are tuples of length 2 consisting of orbital type (e.g. ‘S’, ‘P’ or ‘D’) and a list (per contracted GTO) of tuples of size 2 consisting of the exponent and coefficient. Confused? Well, here’s <tt class="docutils literal"><span class="pre">gbasis</span></tt> for a molecule consisting of a single C atom with a STO-3G basis:</p>
<blockquote>
<div><dl class="docutils">
<dt>[ # per atom</dt>
<dd><dl class="first docutils">
<dt>[</dt>
<dd><dl class="first last docutils">
<dt>(‘S’, [</dt>
<dd>(71.616837, 0.154329),
(13.045096, 0.535328),
(3.530512, 0.444635),
]),</dd>
<dt>(‘S’, [</dt>
<dd>(2.941249, -0.099967),
(0.683483, 0.399513),
(0.222290, 0.700115),
]),</dd>
<dt>(‘P’, [</dt>
<dd>(2.941249, 0.155916),
(0.683483, 0.607684),
(0.222290, 0.391957),
]),</dd>
</dl>
</dd>
</dl>
<p class="last">]</p>
</dd>
</dl>
<p>]</p>
</div></blockquote>
<p>For D and F functions there is an important distinction between pure (5D, 7F) or Cartesian (6D, 10F) functions. PyQuante can only handle Cartesian functions, but we should extract this information in any case, and perhaps work to extend the PyQuante basis set format to include this.</p>
<p><strong>Gaussian</strong>: the <a class="reference external" href="http://www.gaussian.com/g_tech/g_ur/k_gfinput.htm">GFINPUT</a> keyword should normally be used (<a class="reference external" href="http://www.gaussian.com/g_tech/g_ur/k_gfprint.htm">GFPRINT</a> gives equivalent information in a different format and is supported in cclib after v1.2).</p>
<p><strong>GAMESS/GAMESS-UK</strong>: no special keywords are required, but the basis is only available for symmetry inequivalent atoms. There does not seem to be any way to get GAMESS to say which atoms are related through symmetry. As a result, if you want to get basis set info for every atom, you need to reduce the symmetry to C1.</p>
<p><strong>Jaguar</strong>: for more information see manual (for example at <a class="reference external" href="http://yfaat.ch.huji.ac.il/jaguar-help/mand.html#114223">http://yfaat.ch.huji.ac.il/jaguar-help/mand.html#114223</a>)</p>
<p><strong>ORCA</strong>: include <tt class="docutils literal"><span class="pre">Print[</span> <span class="pre">P_Basis</span> <span class="pre">]</span> <span class="pre">2</span></tt> in the <tt class="docutils literal"><span class="pre">output</span></tt> block</p>
</div>
<div class="section" id="geotargets">
<span id="index-4"></span><h2>geotargets<a class="headerlink" href="#geotargets" title="Permalink to this headline">¶</a></h2>
<p>Geotargets are the target values of the criteria used to determine whether a geometry optimisation has converged. The targets are stored in an array of length <tt class="docutils literal"><span class="pre">n</span></tt>, where <tt class="docutils literal"><span class="pre">n</span></tt> is the number of targets, and the actual values of these criteria are stored for every optimisation step in the attribute <a class="reference internal" href="#geovalues">geovalues</a>. Note that cclib does not carry information about the meaning of these criteria, and it is up to the user to interpret the values properly for a particular program. Below we provide some details for several parsers, but it is always a good idea to refer to the source documentation.</p>
<p>In some special cases, the values in <tt class="docutils literal"><span class="pre">geotargets</span></tt> will be <a class="reference external" href="http://docs.scipy.org/doc/numpy-1.8.1/user/misc.html#ieee-754-floating-point-special-values">numpy.inf</a>.</p>
<p><strong>GAMESS UK</strong>: the criteria used for geometry convergence are based on the <tt class="docutils literal"><span class="pre">TOL</span></tt> parameter, which can be set using the <tt class="docutils literal"><span class="pre">XTOLL</span></tt> directive. The fault value of this parameter and the conditions required for convergence vary among the various optimisation strategies (see the <a href="#id3"><span class="problematic" id="id4">`GAMESS-UK manual section on controlling optimisation`_</span></a> for details). In <tt class="docutils literal"><span class="pre">OPTIMIZE</span></tt> mode, <tt class="docutils literal"><span class="pre">TOL</span></tt> defaults to 0.003 and the conditions are,</p>
<blockquote>
<div><ul class="simple">
<li>maximum change in variables below TOL,</li>
<li>average change in variables smaller than TOL * 2/3,</li>
<li>maximum gradient below TOL * 1/4,</li>
<li>average gradient below TOL * 1/6.</li>
</ul>
</div></blockquote>
<p><strong>Jaguar</strong> has several geometry convergence criteria,</p>
<blockquote>
<div><ul class="simple">
<li>gconv1: maximum element of gradient (4.5E-04)</li>
<li>gconv2: rms of gradient elements (3.0E-04)</li>
<li>gconv5: maximum element of nuclear displacement (1.8E-03)</li>
<li>gconv6: rms of nuclear displacement elements (1.2E-03)</li>
<li>gconv7: difference between final energies from previous and current geometry optimisation iterations (5.0E-05)</li>
</ul>
</div></blockquote>
<p>Note that a value for gconv7 is not available until the second iteration, so it is set to zero in the first element of <a class="reference internal" href="#geovalues">geovalues</a>.</p>
<p><strong>Molpro</strong> has custom convergence criteria, as described in the <a class="reference external" href="https://www.molpro.net/info/2012.1/doc/manual/node592.html">manual</a>:</p>
<blockquote>
<div>The standard MOLPRO convergency criterion requires the maximum component of the gradient to be less then <span class="math">\(3 \cdot 10^{-4}\)</span> [a.u.] and the maximum energy change to be less than <span class="math">\(1 \cdot 10^{-6}\)</span> [H] or the maximum component of the gradient to be less then $ 3 cdot 10^{-4}$ [a.u.] and the maximum component of the step to be less then <span class="math">\(3 \cdot 10^{-4}\)</span> [a.u.].</div></blockquote>
<p><strong>ORCA</strong> tracks the change in energy as well as RMS and maximum gradients and displacements. As of version 3.0, an optimisation is considered converged when all the tolerances are met, and there are four exceptions:</p>
<blockquote>
<div><ul class="simple">
<li>the energy is within 25x the tolerance and all other criteria are met</li>
<li>the gradients are overachieved (1/3 of the tolerance) and displacements are reasonable (at most 3x the tolerance)</li>
<li>the displacements are overachieved (1/3 of the tolerance) and the gradients are reasonable (at most 3x the tolerance)</li>
<li>the energy gradients and internal coordinates are converged (bond distances, angles, dihedrals and impropers)</li>
</ul>
</div></blockquote>
<p><strong>Psi</strong> normally tracks five different values, as described <a class="reference external" href="http://sirius.chem.vt.edu/psi4manual/latest/optking.html">in the documentation</a>, but their use various depending on the strategy employed. The default strategy (QCHEM) check whether the maximum force is converged and if the maximum energy change or displacement is converged. Additionally, to aid with flat potential energy surfaces, convergence is as assumed when the root mean square force converged to 0.01 of its default target. Note that Psi print values even for targets that are not being used – in these cases the targets are parsed as <a class="reference external" href="http://docs.scipy.org/doc/numpy-1.8.1/user/misc.html#ieee-754-floating-point-special-values">numpy.inf</a> so that they can still be used (any value will be converged).</p>
</div>
<div class="section" id="geovalues">
<span id="index-5"></span><h2>geovalues<a class="headerlink" href="#geovalues" title="Permalink to this headline">¶</a></h2>
<p>These are the current values for the criteria used to determine whether a geometry has converged in the course of a geometry optimisation. It is an array of dimensions <tt class="docutils literal"><span class="pre">m</span> <span class="pre">x</span> <span class="pre">n</span></tt>, where <tt class="docutils literal"><span class="pre">m</span></tt> is the number of geometry optimisation iterations and <tt class="docutils literal"><span class="pre">n</span></tt> the number of target criteria.</p>
<p>Note that many programs print atomic coordinates before and after a geomtry optimisation, which means that there will not necessarily be <tt class="docutils literal"><span class="pre">m</span></tt> elements in <a href="#id1"><span class="problematic" id="id2">``</span></a>atomcoords``_.</p>
<p>If the optimisation has finished successfully, the values in the last row should be smaller than the values in <a class="reference internal" href="#geotargets">geotargets</a> (unless the convergence criteria require otherwise).</p>
</div>
<div class="section" id="hessian">
<h2>hessian<a class="headerlink" href="#hessian" title="Permalink to this headline">¶</a></h2>
<p>An array of rank 1 that contains the elements of [<a class="reference external" href="http://en.wikipedia.org/wiki/Hessian_matrix">http://en.wikipedia.org/wiki/Hessian_matrix</a> hessian] or the force constant matrix. Only the lower triangular part of the 3Nx3N matrix is stored (this may change in the future, maybe also only the force-constant , unwighted matrix will be parsed).</p>
<ul class="simple">
<li>currently available only in <tt class="docutils literal"><span class="pre">Molpro</span></tt></li>
</ul>
</div>
<div class="section" id="homos">
<span id="index-6"></span><h2>homos<a class="headerlink" href="#homos" title="Permalink to this headline">¶</a></h2>
<p>A 1D array that holds the indexes of the highest occupied molecular orbitals (HOMOs), which contains one element for restricted and two elements for unrestricted calculations. These indexes can be applied to other attributes describing molecular orbitals, such as <a class="reference internal" href="#moenergies">moenergies</a> and <a class="reference internal" href="#mocoeffs">mocoeffs</a>.</p>
</div>
<div class="section" id="mocoeffs">
<span id="index-7"></span><h2>mocoeffs<a class="headerlink" href="#mocoeffs" title="Permalink to this headline">¶</a></h2>
<p>A list of rank 2 arrays containing the molecular orbital (MO) coefficients. The list is of length 1 for restricted calculations, but length 2 for unrestricted calculations. For the array(s) in the list, the first axis corresponds to molecular orbitals, and the second corresponds to basis functions.</p>
<p>Examples:</p>
<ul class="simple">
<li><tt class="docutils literal"><span class="pre">mocoeffs[0][2,5]</span></tt> – The coefficient of the 6th basis function of the 3rd alpha molecular orbital</li>
<li><tt class="docutils literal"><span class="pre">mocoeffs[1][:,0]</span></tt> – An array of the 1st basis function coefficients for the every beta molecular orbital</li>
</ul>
<p>Note: For restricted calculation, <tt class="docutils literal"><span class="pre">mocoeffs</span></tt> is still a list, but it only contains a single rank 2 array so you access the matrix with mocoeffs[0].</p>
<p><strong>GAMESS-UK</strong> - the <a class="reference external" href="http://www.cfs.dl.ac.uk/docs/html/part3/node8.html#SECTION00083000000000000000">FORMAT HIGH</a> directive needs to be included if you want information on all of the eigenvalues to be available. In versions before 8.0 for unrestricted calculations, <tt class="docutils literal"><span class="pre">FORMAT</span> <span class="pre">HIGH</span></tt> does not increase the number of orbitals for which the molecular orbital coefficents are printed, so that there may be more orbital information on the alpha orbitals compared to the beta orbitals, and as a result the extra beta molecular orbital coefficients for which information is not available will be padded out with zeros by cclib.</p>
<p><strong>Molpro</strong> - does not print MO coefficients at all by default, and you must add in the input <tt class="docutils literal"><span class="pre">GPRINT,ORBITALS</span></tt>. What’s more, this prints only the occupied orbitals, and to get virtuals add also <tt class="docutils literal"><span class="pre">ORBPTIN,NVIRT</span></tt>, where <tt class="docutils literal"><span class="pre">NVIRT</span></tt> is how many virtuals to print (can be a large number like 99999 to print all).</p>
</div>
<div class="section" id="moenergies">
<span id="index-8"></span><h2>moenergies<a class="headerlink" href="#moenergies" title="Permalink to this headline">¶</a></h2>
<p>A list of rank 1 arrays containing the molecular orbital energies in eV. The list is of length 1 for restricted calculations, but length 2 for unrestricted calculations.</p>
<p><strong>GAMESS-UK</strong>: similar to <a class="reference internal" href="#mocoeffs">mocoeffs</a>, the directive <a class="reference external" href="http://www.cfs.dl.ac.uk/docs/html/part3/node8.html#SECTION00083000000000000000">FORMAT HIGH</a> needs to be used if you want all of the eigenvalues printed.</p>
<p><strong>Jaguar</strong>: the first ten virtual orbitals are printed by default. In order to print more, use the <tt class="docutils literal"><span class="pre">ipvirt</span></tt> keyword, with <tt class="docutils literal"><span class="pre">ipvirt=-1</span></tt> printing all virtual orbitals.</p>
</div>
<div class="section" id="moments">
<span id="index-9"></span><h2>moments<a class="headerlink" href="#moments" title="Permalink to this headline">¶</a></h2>
<p>This attribute contains the dipole moment vector and any higher electrostatic multipole moments for the whole molecule. It comprises a list of one dimensional arrays,</p>
<ul class="simple">
<li>the first is the reference point used in the multipole expansion, which is normally the center of mass,</li>
<li>the second is the dipole moment vector, in Debyes (<span class="math">\(\mathbf{\mathrm{D}}\)</span>),</li>
<li>the third array contains the raw molecular quadrupole moments in lexicographical order, that is the XX, XY, XZ, YY, YZ and ZZ moments, in Buckinghams (<span class="math">\(\mathbf{\mathrm{B}}\)</span>),</li>
<li>any further arrays contain the raw molecular multipole moments of higher rank, in lexicographical order and in units of <span class="math">\(\mathbf{\mathrm{D}} \cdot Å^{L-1} = 10^{-10} \mathrm{esu} \cdot Å^L\)</span></li>
</ul>
<p>Note that by default cclib will provide the last moments printed, if several are printed in the course of a geometry optimisation or other job type involving several more than one geometry. For post-Hartree-Fock calculations, such as MP2 or coupled cluster, the uncorrelated moments are reported if none are printed for the final wavefunction.</p>
</div>
<div class="section" id="mosyms">
<span id="index-10"></span><h2>mosyms<a class="headerlink" href="#mosyms" title="Permalink to this headline">¶</a></h2>
<p>For unrestricted calculations, this is a list of two lists containing alpha and beta symmetries (i.e. <tt class="docutils literal"><span class="pre">[[alpha_syms],[beta_syms]]</span></tt>) containing strings for the orbital symmetries, arranged in order of energy. In a restricted calculation, there is only one nested list (<tt class="docutils literal"><span class="pre">[[syms]]</span></tt>).</p>
<p>The symmetry labels are normalised and cclib reports standard symmetry names:</p>
<blockquote>
<div><table border="1" class="docutils">
<colgroup>
<col width="13%" />
<col width="13%" />
<col width="13%" />
<col width="18%" />
<col width="33%" />
<col width="11%" />
</colgroup>
<thead valign="bottom">
<tr class="row-odd"><th class="head">cclib</th>
<th class="head">ADF</th>
<th class="head">GAMESS</th>
<th class="head">GAMESS-UK</th>
<th class="head">Gaussian</th>
<th class="head">Jaguar</th>
</tr>
</thead>
<tbody valign="top">
<tr class="row-even"><td>A</td>
<td>A</td>
<td>A</td>
<td>a</td>
<td>A</td>
<td>A</td>
</tr>
<tr class="row-odd"><td>A1</td>
<td>A1</td>
<td>A1</td>
<td>a1</td>
<td>A1</td>
<td>A1</td>
</tr>
<tr class="row-even"><td>Ag</td>
<td>A.g</td>
<td>AG</td>
<td>ag</td>
<td>AG</td>
<td>Ag</td>
</tr>
<tr class="row-odd"><td>A’</td>
<td>AA</td>
<td>A’</td>
<td>a’</td>
<td>A’</td>
<td>Ap</td>
</tr>
<tr class="row-even"><td>A”</td>
<td>AAA</td>
<td>A’ ‘</td>
<td>a” or a’ ‘</td>
<td>A”</td>
<td>App</td>
</tr>
<tr class="row-odd"><td>A1’</td>
<td>AA1</td>
<td>A1’</td>
<td>a1’</td>
<td>A1’</td>
<td>A1p</td>
</tr>
<tr class="row-even"><td>A1”</td>
<td>AAA1</td>
<td>A1”</td>
<td>a1”</td>
<td>A1”</td>
<td>A1pp</td>
</tr>
<tr class="row-odd"><td>sigma</td>
<td>Sigma</td>
<td> </td>
<td> </td>
<td>SG</td>
<td> </td>
</tr>
<tr class="row-even"><td>pi</td>
<td>Pi</td>
<td> </td>
<td> </td>
<td>PI</td>
<td> </td>
</tr>
<tr class="row-odd"><td>phi</td>
<td>Phi</td>
<td> </td>
<td> </td>
<td>PHI (inferred)</td>
<td> </td>
</tr>
<tr class="row-even"><td>delta</td>
<td>Delta</td>
<td> </td>
<td> </td>
<td>DLTA but DLTU/DLTG</td>
<td> </td>
</tr>
<tr class="row-odd"><td>sigma.g</td>
<td>Sigma.g</td>
<td> </td>
<td> </td>
<td>SGG</td>
<td> </td>
</tr>
</tbody>
</table>
</div></blockquote>
<ul class="simple">
<li>ADF - the full list can be found [<a class="reference external" href="http://www.scm.com/Doc/Doc2005.01/ADF/ADFUsersGuide/page339.html">http://www.scm.com/Doc/Doc2005.01/ADF/ADFUsersGuide/page339.html</a> here].</li>
<li>GAMESS-UK - to get the list, ‘grep “data yr” input.m’ if you have access to the source. Note that for E, it’s split into “e1+” and “e1-” for instance.</li>
<li>Jaguar - to get the list, look at the examples in schrodinger/jaguar-whatever/samples if you have access to Jaguar. Note that for E, it’s written as E1pp/Ap, for instance.</li>
<li>NWChem - if molecular symmetry is turned off or set to C1, symmetry adaption for orbitals is also deactivated, and can be explicitely turned on with <cite>adapt on</cite> in the SCF block</li>
</ul>
<p>Developers:
* The use of a function with doctests for each of these cases is recommended, to make sure that the conversion is robust. There is a prototype called normalisesym() in logfileparser.py which should be overwritten in the subclasses if necessary (there is a unittest to make sure that this has been done).
* The character tables [<a class="reference external" href="http://www.mpip-mainz.mpg.de/~gelessus/group.html">http://www.mpip-mainz.mpg.de/~gelessus/group.html</a> here] may be useful in determining the correspondence between the labels used by the comp chem package and the commonly-used symbols.</p>
</div>
<div class="section" id="mpenergies">
<span id="index-11"></span><h2>mpenergies<a class="headerlink" href="#mpenergies" title="Permalink to this headline">¶</a></h2>
<p>The attribute <tt class="docutils literal"><span class="pre">mpenergies</span></tt> holds the total molecule energies including Møller-Plesset correlation energy corrections in a two-dimensional array. The array’s shape is (n,L), where <tt class="docutils literal"><span class="pre">n</span></tt> is 1 for single point calculations and larger for optimisations, and <tt class="docutils literal"><span class="pre">L</span></tt> is the order at which the correction is truncated. The order of elements is ascending, so a single point MP5 calculation will yield mpenergies as <span class="math">\(E_{MP2}, E_{MP3}, E_{MP4}, E_{MP5}\)</span>.</p>
<p><strong>ADF</strong>: does not perform such calculations.</p>
<p><strong>GAMESS</strong>: second-order corrections (MP2) are available in GAMESS-US, and MP2 through MP3 calculations in PC-GAMESS (use <tt class="docutils literal"><span class="pre">mplevl=n</span></tt> in the <tt class="docutils literal"><span class="pre">$contrl</span></tt> section).</p>
<p><strong>GAMESS-UK</strong>: MP2 through MP3 corrections are available.</p>
<p><strong>Gaussian</strong>: MP2 through MP5 energies are available using the <tt class="docutils literal"><span class="pre">MP</span></tt> keyword. For MP4 corrections, the energy with the most substitutions is used (SDTQ by default).</p>
<p><strong>Jaguar</strong>: the LMP2 is available.</p>
</div>
<div class="section" id="mult">
<h2>mult<a class="headerlink" href="#mult" title="Permalink to this headline">¶</a></h2>
<p>The attribute <tt class="docutils literal"><span class="pre">mult</span></tt> is an integer and represents the spin multiplicity of the calculated system, which in turn is the total spin plus one.</p>
</div>
<div class="section" id="natom">
<h2>natom<a class="headerlink" href="#natom" title="Permalink to this headline">¶</a></h2>
<p><tt class="docutils literal"><span class="pre">Natom</span></tt> is an integer, the number of atoms treated in the calculation.</p>
</div>
<div class="section" id="nbasis">
<span id="index-12"></span><h2>nbasis<a class="headerlink" href="#nbasis" title="Permalink to this headline">¶</a></h2>
<p>An integer representing the number of basis functions used in the calculation.</p>
</div>
<div class="section" id="nmo">
<span id="index-13"></span><h2>nmo<a class="headerlink" href="#nmo" title="Permalink to this headline">¶</a></h2>
<p>The number of molecular orbitals in the calculation. It is an integer and is typically equal to <a class="reference internal" href="#nbasis">nbasis</a>, but may be less than this if a linear dependency was identified between the basis functions.</p>
<p>Commands to get information on all orbitals:</p>
<p><strong>GAMESS-UK</strong>: only usually prints information on the 5 lowest virtual orbitals. “FORMAT HIGH” should make it do this for all of the orbitals, although GAMESS-UK 7.0 has a bug that means that this only works for restricted calculations.</p>
<p><strong>Jaguar</strong>: the first ten virtual orbitals are printed by default; in order to print more of them, use the <tt class="docutils literal"><span class="pre">ipvirt</span></tt> keyword in the input file, with <tt class="docutils literal"><span class="pre">ipvirt=-1</span></tt> printing all virtual orbitals (see the [<a class="reference external" href="http://www.pdc.kth.se/doc/jaguar4.1/html/manual/mang.html#644675">http://www.pdc.kth.se/doc/jaguar4.1/html/manual/mang.html#644675</a> manual] for more information).</p>
</div>
<div class="section" id="optdone">
<h2>optdone<a class="headerlink" href="#optdone" title="Permalink to this headline">¶</a></h2>
<p>Flags whether a geometry optimisation has completed. Currently this attribute is a single Boolean value, which is set to True when the final <a class="reference internal" href="#atomcoords">atomcoords</a> represent a converged geometry optimisation. In the future, <tt class="docutils literal"><span class="pre">optdone</span></tt> will be a list that indexes which elements of <a class="reference internal" href="#atomcoords">atomcoords</a> represent converged geometries. This functionality can be used starting from version 1.3, from the command line by passing the <tt class="docutils literal"><span class="pre">--future</span></tt> option to <tt class="docutils literal"><span class="pre">ccget</span></tt>,</p>
<div class="highlight-bash"><div class="highlight"><pre><span class="nv">$ </span>ccget optdone data/Gaussian/basicGaussian09/dvb_gopt.out
Attempting to parse data/Gaussian/basicGaussian09/dvb_gopt.out
optdone:
True
<span class="nv">$ </span>ccget --future optdone data/Gaussian/basicGaussian09/dvb_gopt.out
Attempting to parse data/Gaussian/basicGaussian09/dvb_gopt.out
optdone:
<span class="o">[</span>4<span class="o">]</span>
</pre></div>
</div>
<p>or by providing the corresponding argument to <tt class="docutils literal"><span class="pre">ccopen</span></tt>,</p>
<div class="highlight-python"><div class="highlight"><pre><span class="kn">from</span> <span class="nn">cclib.parser</span> <span class="kn">import</span> <span class="n">ccopen</span>
<span class="n">parser</span> <span class="o">=</span> <span class="n">ccopen</span><span class="p">(</span><span class="s">"filename"</span><span class="p">,</span> <span class="n">optdone_as_list</span><span class="o">=</span><span class="bp">True</span><span class="p">)</span> <span class="c"># could also do future=True instead of optdone_as_list</span>
<span class="n">data</span> <span class="o">=</span> <span class="n">parser</span><span class="o">.</span><span class="n">parse</span><span class="p">()</span>
</pre></div>
</div>
</div>
<div class="section" id="scfenergies">
<h2>scfenergies<a class="headerlink" href="#scfenergies" title="Permalink to this headline">¶</a></h2>
<p>An array containing the converged SCF energies of the calculation, in eV. For an optimisation log file, there will be as many elements in this array as there were optimisation steps.</p>
<p><strong>Molpro</strong>: typically prints output about geometry optimisation in a separate logfile. So, both that and the initial output need to be passed to the cclib parser.</p>
</div>
<div class="section" id="scftargets">
<h2>scftargets<a class="headerlink" href="#scftargets" title="Permalink to this headline">¶</a></h2>
<p>Target thesholds for determining whether the current SCF run has converged, stored in a <tt class="docutils literal"><span class="pre">n</span> <span class="pre">x</span> <span class="pre">m</span></tt> array, where <tt class="docutils literal"><span class="pre">n</span></tt> is the number of geometry optimisation steps (1 for a single point calculation) and <tt class="docutils literal"><span class="pre">m</span></tt> is the number of criteria. The criteria vary between programs, and depending on the program they may be constant for the whole of a geometry optimisation or they may change between optimisation steps. A more complete description for each program follows.</p>
<p><strong>ADF</strong>: There are two convergence criteria which are controlled by <tt class="docutils literal"><span class="pre">SCFcnv</span></tt> in the <a class="reference external" href="http://www.scm.com/Doc/Doc2014/ADF/ADFUsersGuide/page235.html#keyscheme%20INTEGRATION">CONVERGE subkey of the SCF block</a>.</p>
<ul class="simple">
<li>The maximum element of the commutator of the Fock matrix and P-matrix needs to be below <tt class="docutils literal"><span class="pre">SCFcnv</span></tt>.</li>
<li>The norm of the same matrix needs to be below <tt class="docutils literal"><span class="pre">10*SCFcnv</span></tt>.</li>
</ul>
<p>This hard target is normally used for single point calculations and the last step of geometry optimisations, and it defaults to 1.0E-6. There is also a soft target <tt class="docutils literal"><span class="pre">scfconv2</span></tt> that defaults to 1.0E-3, which can be switched on and is used by ADF automatically in some cases such as the first step in a geometry optimization.</p>
<p>For intermediate steps in a geometry optimisation the situation is more complicated and depends on the gradient and the integration accuracy. A post on the ADF user’s forum revealed that it is calculated as follows:</p>
<div class="math">
\[\mathrm{new\,criteria} = max( \mathrm{SCFcnv}, \, min(\mathrm{old\,criteria}, \, \mathrm{grdmax}/30, 10^{-\mathrm{accint}})) ),\]</div>
<p>where <tt class="docutils literal"><span class="pre">old</span> <span class="pre">criteria</span></tt> is the initial value or from the previous geometry cycle, <tt class="docutils literal"><span class="pre">grdmax</span></tt> is the maximum gradient from the last geometry step and <tt class="docutils literal"><span class="pre">accint</span></tt> is the current integration accuracy.</p>
<p><strong>GAMESS</strong>: Two criteria are, the maximum and root-mean-square (RMS) density matrix change, are used with a default starting value of 5.0E-05. It seems these values can change over the course of a geometry optimisation. ROHF calculations use SQCDF instead of the standard RMS change.</p>
<p><strong>GAMESS-UK</strong>: According to <a class="reference external" href="http://www.cfs.dl.ac.uk/docs/html/part4/node6.html">the manual</a>, convergence is determined by convergence of density matrix elements. The default value for SCF is 1E-5, but it appears to be 1E-7 for geoopts.</p>
<p><strong>Gaussian</strong>: normally three criteria are used.</p>
<ul class="simple">
<li>The RMS change in the density matrix elements, with a default of 1.0E-4 (1.0E-8 for geo opts).</li>
<li>Maximum change in the density matrix elements, with a default of 1.0E-2 (1.0E-6 for geo opts).</li>
<li>The change in energy, with a default threshold of 5.0E-05 (1.0E-06 for geo opts).</li>
</ul>
<p><strong>Jaguar 4.2</strong>: The targets in Jaguar 4.2 (based on the manual) depend on whether the job is a geometry optimisation or not. For geometry optimisations and hyper/polarisability calculation, the RMS change in the density matrix elements is used as a criterion (controlled by the <tt class="docutils literal"><span class="pre">dconv</span></tt> keyword), with a default of 5.0E6.
The energy convergence criterion (keyword <tt class="docutils literal"><span class="pre">econv</span></tt>) is ignored for geometry optimisation calculations but is used for SCF calculations, and the default in this case is 5.0E5, except for hyper/polarisability calcualtions where it is 1.0E6.</p>
</div>
<div class="section" id="scfvalues">
<h2>scfvalues<a class="headerlink" href="#scfvalues" title="Permalink to this headline">¶</a></h2>
<p>The attribute <tt class="docutils literal"><span class="pre">scfvalues</span></tt> is a list of arrays of dimension <tt class="docutils literal"><span class="pre">n</span> <span class="pre">x</span> <span class="pre">m</span></tt> (one element for each step in a geometry optimisation), where <tt class="docutils literal"><span class="pre">n</span></tt> is the number of SCF cycles required for convergence and <tt class="docutils literal"><span class="pre">m</span></tt> is the number of SCF convergence target criteria. For some packages, you may need to include a directive to make sure that SCF convergence information is printed to the log file</p>
<p><strong>Gaussian</strong>: requires the <a class="reference external" href="http://www.gaussian.com/g_tech/g_ur/k_route.htm">route section</a> to start with #P</p>
<p><strong>GAMESS-UK</strong>: convergence information is printed only for the first optimisation step by default, but can be forced at all steps by adding <tt class="docutils literal"><span class="pre">IPRINT</span> <span class="pre">SCF</span></tt> to the input file.</p>
</div>
<div class="section" id="vibdisps">
<h2>vibdisps<a class="headerlink" href="#vibdisps" title="Permalink to this headline">¶</a></h2>
<p>The attribute <tt class="docutils literal"><span class="pre">vibdisps</span></tt> stores the Cartesian displacement vectors from the output of a vibrational frequency calculation. It is a rank 3 array having dimensions <tt class="docutils literal"><span class="pre">M</span> <span class="pre">x</span> <span class="pre">N</span> <span class="pre">x</span> <span class="pre">3</span></tt>, where <tt class="docutils literal"><span class="pre">M</span></tt> is the number of normal modes and <tt class="docutils literal"><span class="pre">N</span></tt> is the number of atoms. <tt class="docutils literal"><span class="pre">M</span></tt> is typically <tt class="docutils literal"><span class="pre">3N-6</span></tt> (<tt class="docutils literal"><span class="pre">3N-5</span></tt> for linear molecules).</p>
</div>
</div>
</div>
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
<a href="methods.html" class="btn btn-neutral float-right" title="Calculation methods" accesskey="n">Next <span class="fa fa-arrow-circle-right"></span></a>
<a href="data.html" class="btn btn-neutral" title="Parsed data (version 1.3.1)" accesskey="p"><span class="fa fa-arrow-circle-left"></span> Previous</a>
</div>
<hr/>
<div role="contentinfo">
<p>
© Copyright 2014-2015, cclib Development Team.
</p>
</div>
Built with <a href="http://sphinx-doc.org/">Sphinx</a> using a <a href="https://github.com/snide/sphinx_rtd_theme">theme</a> provided by <a href="https://readthedocs.org">Read the Docs</a>.
</footer>
</div>
</div>
</section>
</div>
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT:'./',
VERSION:'1.3.1',
COLLAPSE_INDEX:false,
FILE_SUFFIX:'.html',
HAS_SOURCE: true
};
</script>
<script type="text/javascript" src="_static/jquery.js"></script>
<script type="text/javascript" src="_static/underscore.js"></script>
<script type="text/javascript" src="_static/doctools.js"></script>
<script type="text/javascript" src="http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML"></script>
<script type="text/javascript" src="_static/js/theme.js"></script>
<script type="text/javascript">
jQuery(function () {
SphinxRtdTheme.StickyNav.enable();
});
</script>
</body>
</html>