ViewVC Help
View File | Revision Log | Show Annotations | View Changeset | Root Listing
root/group/trunk/OOPSE-4/src/UseTheForce/SHAPES_FF.cpp
Revision: 2759
Committed: Wed May 17 21:51:42 2006 UTC (18 years, 1 month ago) by tim
File size: 5689 byte(s)
Log Message:
Adding single precision capabilities to c++ side

File Contents

# Content
1 /*
2 * Copyright (c) 2005 The University of Notre Dame. All Rights Reserved.
3 *
4 * The University of Notre Dame grants you ("Licensee") a
5 * non-exclusive, royalty free, license to use, modify and
6 * redistribute this software in source and binary code form, provided
7 * that the following conditions are met:
8 *
9 * 1. Acknowledgement of the program authors must be made in any
10 * publication of scientific results based in part on use of the
11 * program. An acceptable form of acknowledgement is citation of
12 * the article in which the program was described (Matthew
13 * A. Meineke, Charles F. Vardeman II, Teng Lin, Christopher
14 * J. Fennell and J. Daniel Gezelter, "OOPSE: An Object-Oriented
15 * Parallel Simulation Engine for Molecular Dynamics,"
16 * J. Comput. Chem. 26, pp. 252-271 (2005))
17 *
18 * 2. Redistributions of source code must retain the above copyright
19 * notice, this list of conditions and the following disclaimer.
20 *
21 * 3. Redistributions in binary form must reproduce the above copyright
22 * notice, this list of conditions and the following disclaimer in the
23 * documentation and/or other materials provided with the
24 * distribution.
25 *
26 * This software is provided "AS IS," without a warranty of any
27 * kind. All express or implied conditions, representations and
28 * warranties, including any implied warranty of merchantability,
29 * fitness for a particular purpose or non-infringement, are hereby
30 * excluded. The University of Notre Dame and its licensors shall not
31 * be liable for any damages suffered by licensee as a result of
32 * using, modifying or distributing the software or its
33 * derivatives. In no event will the University of Notre Dame or its
34 * licensors be liable for any lost revenue, profit or data, or for
35 * direct, indirect, special, consequential, incidental or punitive
36 * damages, however caused and regardless of the theory of liability,
37 * arising out of the use of or inability to use software, even if the
38 * University of Notre Dame has been advised of the possibility of
39 * such damages.
40 */
41
42 #include "UseTheForce/DarkSide/shapes_interface.h"
43 #include "UseTheForce/DarkSide/lj_interface.h"
44 #include "UseTheForce/DarkSide/sticky_interface.h"
45 #include "UseTheForce/ForceFieldFactory.hpp"
46 #include "io/OptionSectionParser.hpp"
47 #include "io/DirectionalAtomTypesSectionParser.hpp"
48 #include "io/AtomTypesSectionParser.hpp"
49 #include "io/LennardJonesAtomTypesSectionParser.hpp"
50 #include "io/ChargeAtomTypesSectionParser.hpp"
51 #include "io/MultipoleAtomTypesSectionParser.hpp"
52 #include "io/ShapeAtomTypesSectionParser.hpp"
53 #include "io/StickyAtomTypesSectionParser.hpp"
54 #include "io/BondTypesSectionParser.hpp"
55 #include "io/BendTypesSectionParser.hpp"
56 #include "io/TorsionTypesSectionParser.hpp"
57 #include "UseTheForce/ForceFieldCreator.hpp"
58 #include "UseTheForce/SHAPES_FF.hpp"
59 #include "utils/simError.h"
60 namespace oopse {
61
62 SHAPES_FF::SHAPES_FF(){
63
64 //set default force field filename
65 setForceFieldFileName("Shapes.frc");
66
67 //The ordering of section parsers is important...
68 //OptionSectionParser must come first to set options for other parsers
69 //DirectionalAtomTypesSectionParser should be before
70 //AtomTypesSectionParser since these two section parsers will actually
71 //create "real" AtomTypes (AtomTypesSectionParser will create AtomType
72 //and DirectionalAtomTypesSectionParser will create DirectionalAtomType
73 //which is a subclass of AtomType, therefore it should come first). Other
74 //AtomTypes Section Parser will not create the "real" AtomType, they only
75 //add and set some attribute of the AtomType. Thus the ordering of these
76 //are not important. AtomTypesSectionParser should be added before other atom
77 //type section parsers. Make sure they are added after
78 //DirectionalAtomTypesSectionParser and AtomTypesSectionParser. The order
79 //of BondTypesSectionParser, BendTypesSectionParser and
80 //TorsionTypesSectionParser are not important.
81 spMan_.push_back(new OptionSectionParser(forceFieldOptions_));
82 spMan_.push_back(new ShapeAtomTypesSectionParser(forceFieldOptions_));
83 spMan_.push_back(new DirectionalAtomTypesSectionParser(forceFieldOptions_));
84 spMan_.push_back(new AtomTypesSectionParser());
85 spMan_.push_back(new LennardJonesAtomTypesSectionParser(forceFieldOptions_));
86 spMan_.push_back(new ChargeAtomTypesSectionParser(forceFieldOptions_));
87 spMan_.push_back(new MultipoleAtomTypesSectionParser(forceFieldOptions_));
88 spMan_.push_back(new StickyAtomTypesSectionParser(forceFieldOptions_));
89 spMan_.push_back(new BondTypesSectionParser(forceFieldOptions_));
90 spMan_.push_back(new BendTypesSectionParser(forceFieldOptions_));
91 spMan_.push_back(new TorsionTypesSectionParser(forceFieldOptions_));
92
93 }
94
95 SHAPES_FF::~SHAPES_FF(){
96 // We need to clean up the fortran side so we don't have bad things happen if
97 // we try to create a second EAM force field.
98 destroyShapeTypes();
99 }
100
101 void SHAPES_FF::parse(const std::string& filename) {
102 ifstrstream* ffStream;
103 ffStream = openForceFieldFile(filename);
104
105 spMan_.parse(*ffStream, *this);
106
107 ForceField::AtomTypeContainer::MapTypeIterator i;
108 AtomType* at;
109
110 for (at = atomTypeCont_.beginType(i); at != NULL; at = atomTypeCont_.nextType(i)) {
111 at->makeFortranAtomType();
112 }
113
114 for (at = atomTypeCont_.beginType(i); at != NULL; at = atomTypeCont_.nextType(i)) {
115 at->complete();
116 }
117
118 int isError = 0;
119 completeShapeFF(&isError);
120
121 delete ffStream;
122 }
123
124
125 // RealType SHAPES_FF::getRcutFromAtomType(AtomType* at){
126 // }
127 } //end namespace oopse
128