CREVICER is a free, open-source occluded region corrosion simulator. Among the many goals of this simulator are the quest to minimize short cuts and "do things right", the quest to learn and advance knowledge, and the quest to have better toys to play with. The idea for CREVICER was born out of dissatisfaction with the state of crevice corrosion modeling in which each researcher needed to start from scratch because of the absence of sharing of code. The focus of the work on CREVICER is to make it less of a project under development, understood and usable only by those intimately familiar with code, and more of a tool employable by anyone familiar with corrosion principles and comfortable with computers.
We have intentionally chosen to keep CREVICER and its source code open, available, and free. In doing so, we are able to take advantage of the efforts of tremendously talented people from around the world. Our approach brings its own unique challenges and difficulties, but we are confident (and other similarly structured projects have demonstrated) that in the long run there are benefits in this approach for science. Because the code is currently under active development, we prefer that everyone get it directly from us. This will permit us to collaborate with all of the users. So for the time being, please refer potential users to us instead of redistributing. This material is based in whole or in part on work supported by the National Science Foundation under Grants DMR-9119304 and DMR-9505760. Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation (NSF).
CREVICER Help Wanted
We are releasing this code because we think that there are other researchers who are able and willing to help us improve it. Please do not hesitate to drop us a note with comments or offering suggestions, or even better, contribute code. Just send email to firstname.lastname@example.org
There are many ways to get involved with the CREVICER project. If you'd like to get involved, we encourage you to find an area where you are interested, discuss a bit about what you are doing and how you are going about it with the other developers, and then go to it.
To keep development synchronized, we'd appreciate if you'd let the developers know in advance what you plan to work on. This way we can make sure that you have the latest versions of the relevant code, we can make sure you understand and benefit from past discussion or thinking on the subject, and also make sure that no one else's work will conflict with yours. It is important to keep close communication so we all know what everyone else is working on and development stays in sync.
If you wish to participate with the CREVICER project, step one is to down load the code and get it to compile on your system C++.
In the current release we are especially looking for feedback in the
Suggestions for future priorities - Are there classes of problems that cannot be adequately diagnosed with the current instruments or tools?
Here are a few assorted goals we'd like to accomplish in the foreseeable
Last modified: June 25, 2002 David Wang