<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="serif">While some of you are making good progress on
re-writing dusty in Fortran, rewriting dusty in C is
significantly more challenging. Here are some pointers (no
pun intended) to get you started.</font></p>
<p><font face="serif">If you want to start our your code in a
segmented form (functions in a different files) that is fine --
but if you are really rusty on C coding, then it may be better
to keep the first version in anvil as one big code file.</font></p>
<p><font face="serif">Personally, I would stay away from things from
the C++ STL. I will show you some of my C++ HPC code later, but
generally if you don't really understand what is going on under
the hood of these entities, then there is no way you will get
the same results as the original dusty. <br>
</font></p>
<p><font face="serif">When I rewrote dusty in C the first time I
seem to remember writing the functions first and then working
down the main progam loop by loop -- testing and comparing the
values between dusty77 and my new C program after each loop. I
recommend that you start this process soon as it is not
something that can normally be done the night before it is due.</font></p>
<p><font face="serif">If memory serves, I think there are ten
different arrays that have to be maintained in the main program
of dusty. If you need a refresher on using calloc/malloc to
create arrays off of the heap in C, please let me know.</font></p>
<p><font face="serif"><br>
</font></p>
<div class="moz-signature">-- <br>
<b><i>Andrew J. Pounds, Ph.D.</i></b><br>
<i>Professor of Chemistry and Computer Science</i><br>
<i>Director of the Computational Science Program</i><br>
<i>Mercer University, Macon, GA 31207 (478) 301-5627</i></div>
</body>
</html>