* Fixed pdb2gmx picking up force field from local instead of
library directory
* Made pdb2gmx vsite generation work again for certain His namings.
* Fixed incorrect virial and pressure averages with certain
nst... values (instantaneous values correct)
* Fixed incorrect cosine viscosity output
* New -multidir alternative for mdrun -multi option
* Several minor fixes in analysis tools
* Several updates to the program documentation
This is maintainance release, it fixes:
* Double precision energy file reading
* CHARMM and GB issues
* Support for Altivec (PowerPC) with CMake
* Running binaries within the CMake build tree is now possible
* Various other issues
Based on PR#43775 by Kamel Derouiche.
5.2 14.07.2004 - Version 5.2 !!!
NEW RELEASE
===========
5.2.rc17 14.07.2004 - Manual sources moved out of the package
- numerous changes in the manual
5.2.rc16 12.07.2004 - Makefile.am: double distclean rule removed
- fflush added before mygets() - because of Windows
- manual spell-checked
- '-consmrel' fixed
- usage message extended
5.2.rc15 09.07.2004 - many changes to the manual
5.2.rc14 01.07.2004 - test suite checked, notice about results added
5.2.rc13 01.07.2004 - a number of small fixes (alloc and dealloc in epe)
- convergence output for user branches fixed
- G-T rate output precision fixed
- tests checked and fixed
5.2.rc12 30.06.2004 - branch length convergence output corrected for
user set branch lengths (i.e. no estimate)
- avergedist updated: output of min/max/var/std.dev.
- tstvratio and yrtsratio - no output for GTR
- some future cmdline flags added to help
- -prefix, -sub50, -randseed moved to usage output
- -randseed=# added
- release date changed in code
5.2.rc11 18.06.2004 - flags to set epsilon values added for debugging
(dependent on USE_ADJUSTABLE_EPS compiler switch)
19.06.2004 - quartet percent computation fixed:
quartet sums moved qinfomatr[0] -> qinfomatr[8]
qinfomatr[0]=missing qs. (release 5.2.rc9)
- character state output added to R/Q matrix output
- average computation of dist-matrix changed:
mean=average, variance, std deviation
TODO: proper output / use Korbis S.E. method
25.06.2004 - GTR model ready, menu order HKY, TN, GTR, (SH), HKY
29.06.2004 - many changes to the manual
5.2.rc10 11.06.2004 - fixed no quartets in parameter estimtion for <4 seqs
15.06.2004 - computation of Bayesian weights moved into
subroutine loglkl2weight.
- use subroutine loglkl2weight in parallel code
-> fixing division by zero bug
5.2.rc9 11.06.2004 - sequence number check for <4 and >257 added
<4 - no quartet methods available
>257 - no quartet puzzling available
- counting for missing quartets added for parallel
message checking (TODO: handling and checking)
- output of root branch name added for clock analysis
(sequence name or "internal branch")
5.2.rc8 04.05.2004 - tree tests move to treetest.c/treetest.h
- comments added
- typo corrected (suset -> subset)
08.06.2004 - ELW: continue counting p, when significantly worse
- 1sKH/2sKH: restrict tests to 3 digits (0.00)
(test behaviour: seems not to use some trees (KH),
see above - used, but too low variance)
5.2.rc7 12.02.2004 - corrected typos in usage/README
20.02.2004 - cmdline: prefix flag fixed
22.02.2004 - '-wsr/-wsl' flags fixed: output file
and file name output
5.2.rc6 25.11.2003 - 'FPRINTF...' changed to 'fprintf(STDOUT,'
- strcpy added in openfile-routines
5.2.rc5 25.11.2003 - filename length chack added
- typo FILENAMELENTH corrected
5.2.rc4 19.11.2003 - minor corrections: int/uli comparisons
- SPRNG added to src/sprng
- src/sprng autoconf/automake setup
- Parallel Parameter Estimation (JPDC, Ekki 1)
5.2.rc3 07.11.2003 - WAG Matrix code/docu corrected (Goldman)
TODO: remove additional output for printrmat
TODO: make PEPS* smaller to have better accuracy
in parameter estimation.
5.2.rc2 01.09.2003 - bug from 5.1.pl29 found and eliminated
alloc size wrong: worked if Maxsubset<=Maxspc
TODO: remove out-commented debug messages
5.2.rc1 20.08.2003 - first release candidate for tree-puzzle 5.2
CODE FREEZE
===========
5.1.pl30 20.08.2003 - naming convention changed for manual name input to
use FILENAME.puzzle, ...
5.1.pl29 23.07.2003 - new compiler warnings fixed
- index error naming fixed
- debugging of matrix based permutation (not finished)
5.1.pl28 01.07.2003 - cmdline flags to switch off ml branch lengths
(-notreelh), tree tests (-notreetest)
5.1.pl27 24.06.2003 - output quartet support for incorporated split in
report file
5.1.pl26 06.06.2003 - menu order of tree reconstruction methods altered to
QP, user tree, consensus, dist (no tree)
(last two switched)
5.1.pl25 05.06.2003 - small changes to fix compiler warnings
5.1.pl24 04.06.2003 - changes from benchmark-branch merged:
debug output removed
- checktime fixed: sumtodo <-> done for quartets
5.1.pl23 26.05.2003 - puzzle.c: CONSENSUS -> QUARTPUZ,
allocated unnecessary memory
- additional malloc-checks added (if buffer == NULL)
01.06.2003 - mlmode conditions with readable constants (ml2.c,ml.h)
- garbage collection in tree2bipart/subtree2bipart
5.1.pl22 16.05.2003 - fixing Array Bound Read in fputid
(bug had no effect, but was read before check)
- garbage collection completed in p-step algorithms
and node-label (free_tree/internalnode),
trueIDtmp (allpstep),
- small fix in test script and rebuild of check-files
5.1.pl21 14.05.2003 - fixing free of all allocations in puzzling step
(mrca, recur, split, orig)
5.1.pl20 05.05.2003 - small fix in recursive Alg. (recur.c)
- debug output removed
- cross check removed from (recur.c,mrca.c)
5.1.pl19 27.04.2003 - recursive Alg. (recur.c) fixed:
edge cluster has not to be reconstructed after
adding new leaves only updated.
- debug output removed from recur.c, split.c
- MRCA-based (mrca.c) finished
5.1.pl18 26.04.2003 - recursive (recur.c) finished
TODO: remove debug output
- MRCA (mrca.c) startet
5.1.pl17 25.04.2003 - split-based (split.c) finished
TODO: remove debug output
- recursive (recur.c) startet
5.1.pl16 22.04.2003 - orig pstep alg: updating of edgemap outsourced to
updateedgemap_orig
- writeOTU_orig, writetree_orig, resetedgeinfo_orig,
minimumedgeinfo_orig:
_orig removed, since independent of algorithm type
- onepstep: _orig added (onepstep_orig)
- time check/status output moved to checktime routine.
added to ml step of parallel version
- split.c temporarily added to release
5.1.pl15 18.04.2003 - trueID dependent procedures 'de-trueID-ed'
trueID saved in the tips of the tree.
5.1.pl14 10.04.2003 - consensus stuff moved to consensus.h/.c
- unique tree sorting moved to treesort.h/.c
- changes to pstep-split.h/.c
- changed names of procedures using trueID to
*_trueID
5.1.pl13 07.04.2003 - subsetmatr.[hc] added to process missing data
analyses. (old version, functions in puzzle2)
- deglobalized: guessdatatype, readsequencefile,
getsizesites, initid, getseqs
removed obsolete: getdataset
- moved: output of taxa after input
- computation of Maxbrnch moved from readsequencefile
to inputandinit
- readsubsetfile, permutetaxa_ss added, '-rssm' works
- empty quartets fixed in checkquartet
missing data -> OK, HALT error otherwise
5.1.pl12 04.04.2003 - tests: check-qp-clock regenerated, changes in
Makefile.am and template-test
- obsolete stuff removed: global trueID_orig + alloc,
inittree_orig/freetree_orig from PP_SendDoPermutBlock
PP_slave_do_puzzling (ppuzzle), global _orig
variables (pstep), makenewsplitentries (old),
kh_test (old)
- column variable in tree output routines deglobalized
- copyright headers added to pstep.[hc]
- pstep copied to pstep-{split | mrca | recursive}
- implementation of pstep-split.[ch] started
(done: structure/init, todo: remove _orig stuff)
5.1.pl11 03.04.2003 - tests/Makefile.am: 'build-puzzle failed' fixed
- some changes in test script template
- cleanup: removed obsolete routines
- puzzle module: makenewsplitentriesnew
- ppuzzle module: PP_do_puzzling, PP_SendPermut,
PP_RecvPermut, PP_SendSplits, PP_RecvSplits
- deglobalized: makenewsplitentries, makepart,
computebiparts, copysplit
- parallel puzzling step based on allpstep, onepstep
- time check/status output added to parallel version
(inaccurate since current slave progress not known)
- TIMECHECK_INTERVAL for setting time interval
of status output in ML/puzzling step
- Header when printing 1 PAM rate matrix (-printrmat)
- final pstep copied to pstep-{split | mrca | recursive}
5.1.pl10 02.04.2003 - tests/Makefile.am fixed (TODO: build-puzzle.test)
- Dates/Version adjusted: April 2003/TREE-PUZZLE 5.2
- Dates/Version fixed in doc/*.html, doc/*.tex
- number added to outgroup(menu)/sequence(start) output
- Time measurement only done after each completed
intermediate tree to reduce the the number from
O(Numtrial*n^4) to O(Numtrial) -> less overhead,
but 15min met less accurate.
- quartet support output for splits added in
writeoutputfile for later use (TODO: '#if0'ed)
- (sequential) puzzling step moved from puzzle1.c
to pstep.c: allpstep, onepstep
TODO: parallel puzzling step in ppuzzle.c
(works but with old PP_slave_do_puzzling)
5.1.pl9 31.03.2003 - consensus construction added to menu
- support value computation fixed for phylip tree,
wrong divisor used in consensus
- test directory/Makefile.am/tests created
(make check)
5.1.pl8 30.03.2003 - puzzling step proc's: most variables 'deglobalized'
5.1.pl7 26.03.2003 - original puzzling step out-sourced to pstep-orig.c
and pstep-orig.h
pstep.c, pstep.h (and above) added to Makefile.am
5.1.pl6 25.03.2003 - '-usebranch' option added fr later use
- 'SONJA' added for external parameter estimation
5.1.pl5 24.03.2003 - ml branch length estimation added to consensus option
(todo: plausibility check - is tree file available)
- output for reportfile fixed
- output of likelihood to clocklike tree in treefile
added/fixed
5.1.pl4 21.03.2003 - consensus option added to compute usertree consensus
(only consensus is computed and printed to stdin)
- usertreefile PREFIX fixed
5.1.pl3 20.03.2003 - TP_MAX_EXP_DIFF=b-a>0 introduced, such that
(1.0+exp(a-b) == 1.0) to avoid the computation
as well as possible FPE, when a-b gets very small.
- flag '-prefix=XXX' added: use 'XXX' as filename
prefix instead of 'Infilename'
5.1.pl2 05.12.2002 - PP_Finalized before exit in parallel programs.
5.1.pl1 05.12.2002 - FPE in Brent's algorithm fixed: ()/0, when x=w=v.
5.1 05.11.2002 - Version 5.1 !!!
Based on PR#43776 by Kamel Derouiche for 15.7.
What's new in nut 15.8:
* This release updates the USDA database to include some data corrections for
milk.
* The program's initial data load is now considerably faster.
What's new in nut 15.7:
* This version includes an improvement to the automatic calorie tool to make it
better able to hold fat mass or lean mass constant.
* Also, there is now a facility to explicitly set the ratio between linoleic
and alpha-linolenic acids.
What's new in nut 15.0:
* This release introduces the new USDA Nutrient Database SR22 and allows
current nut installations to have their existing meal records reinterpreted
with the new database.
What's new in nut 14.5a:
* The new feature "Weight Log Regression" does not tell you what you weigh;
what it does is apply linear regression to a series of daily weight and body
fat percentage entries to smooth out the random noise and tell you which
direction your weight is trending, how fast it is going there, and how much
of the change is lean or fat.
Based on PR#43777 by Kamel Derouiche, with some clean up by me.
Version 1.20, 9/3/2008. This version fixes a bug that caused lucy
to fail when there was too much information on the FASTA header lines
in the input files. Lucy had a 256 character buffer for reading
lines from the input files. If any FASTA header lines were longer
than 256 characters, the remaining characters would get read as part
of the FASTA sequence. The solution implemented in this version is
simply to increase the buffer size to 4096 characters. While that
still leaves the potential for the same error to occur with extremely
long header lines, the limitation that this entails seems reasonable,
and this should fix the problem for all pratical purposes.
---------------------------------------------------------------------
Version 1.19, 12/30/2003. This version fixes a bug that could cause
sequences to be rejected incorrectly in the vector detection step
(phase 6). Because of the way that lucy compares "tags" in the
target sequence with "tags" in the vector sequence, some bases in
the target sequence could get counted more than once in the tally
of bases that match the vector sequence. In rare instances, this
could cause the sequence to exceed the minimum threshold for
rejection, as a result of random sequence similarity.
The reporting of the CLB range in the -debug output file has also
been changed. If the CLB range begins with the first base of the
sequence, then the left coordinate of the CLB range will be reported
as 1 (instead of 0). The range "CLB 0 0" still indicates an empty
CLB range.
GROMACS 4.5.1 is bug fix release.
Release notes for 4.5
New features
* Pencil decomposition of the reciprocal space PME grid to
improve scaling. This reduces the amount of communication
for high parallelization and improves load balancing with up
to 40% overall performance improvement for large systems.
* Memory usage is improved for very large systems, allowing
simulations of >100 million atoms.
* Running on a multi-core node now uses thread-based
parallelization to automatically spawn the optimum number of
threads in the default build. MPI is now only required for
parallelization over the network.
* Domain decomposition can now also be used without periodic
boundary conditions
* GPU acceleration support on NVIDIA cards. This first release
with GPU support based on OpenMM provides up to an order of
magnitude faster performance for implicit solvent simulations,
but PME simulations are about as fast as on a high-end CPU.
* Check-pointing is made more secure:MD5sum are used to verify
that all files are correctly in-place before a simulation is
appended. Output file appending at continuation is turned on
by default.
* Increased tolerance for networked file system failures and
cluster node crashes: checkpoint handling is safer and mdrun
forces file system cache flushes during checkpoints.
* Full CMake support. After the 4.5 release we will be
switching the default build tool from autoconf to cmake,
and possibly deprecate autoconf in the future.
* Full support for seven AMBER force fields in the standard
distribution, with default Amber names. We also include the
recent Amber99sb-ildn in the distribution.
* Support for CHARMM27, including cmap for dihedrals
* Efficient Generalized-Born implicit solvent support
including the Still/HCT/OBC-models to compute the Born radii,
a novel way of tabulating the generalized Born-interaction
formula for greater speed, and optimized SSE-routines in both
single and double precision.
* Highly efficient all-vs-all assembly kernels for both vanilla
and generalized born interactions, in both single and double
precision.
* Much better support for nucleic acid simulations, including
automatic handling by pdb2gmx.
* Support for Velocity-Verlet integrators for reversible T-
and P-coupling; MTTK pressure control integrators;
Nose-Hoover chains.
* Symplectic Trotter Leap-Frog integrator for twin-range
non-bonded interactions.
* Support for Bennet acceptance ratio calculations through
direct calculation of Hamiltonian differences during the
simulation.
* File formats: All GROMACS tools can now read any VMD
supported trajectory format, without converting trajectory
first. (VMD libraries are required).
* pdb2gmx now retains the residue numbers from the input,
mdrun and all tools use these original numbers.
New tools
* g_bar: Bennett acceptance ratio (BAR) free energy calculations,
including automatic error estimates and phase space overlap
measures.
* g_rdf was a little bit enhanced that structure factors can
be calculated for any system, by supplying the necessary data
via sfactor.dat. Most of the common atomtypes are already
contained, but everybody who needs more freedom can enhance
the table
* g_select: Library support for "dynamic index groups" based
on textual selections (experimental feature).
See the tool g_select, the included template.c, or Doxygen
documentation for information on how to write analysis tools
using the library. Existing tools have not (yet) been
converted.
* g_tune_pme: For a given number of processes or threads this
tool systematically times mdrun with various numbers of
PME-only nodes and determines which setting is fastest. It
also checks whether performance can be enhanced by shifting
load between the real and the reciprocal space part of the
Ewald sum.
* g_membed: a very convenient utility for rapidly embedding
membrane proteins into equilibrated lipid bilayers
* g_pme_error: estimates the error of the electrostatic forces
if using the SPME algorithm. TO be incorporated in g_tune_pme
Changes that might affect your results
* grompp by default sets the new nstcalcenergy parameter equal
to nstlist, this has no effect on the integration, only on
the energy averages stored in ener.edr
* grompp by default sets the new nsttcouple parameter equal to
nstlist, this means T-coupling is done less frequently;
grompp checks if tau_t is large enough
* grompp by default sets the new nstpcouple parameter equal to
nstlist, this means P-coupling is done less frequently;
grompp checks if tau_p is large enough
* mdrun results with old tpr files with twin-range non-bonded
interactions will be different, because of the new symplectic
integrator
* for free-energy calculations sc-sigma now also sets the minimum
soft-core sigma (old tpr files retain the old behavior,
which can be enforced by setting the env.var. GMX_SCSIGMA_MIN to 0)
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
Based on PR#43388 by Wen Heping.
version 3.69 (September, 2009)
* If there are more than about 50 species in the tree, Treedist can
fail to compute distances among the trees. This is due to an overflow
problem inadvertently introduced in version 3.68. There is no
workaround with the 3.68 executable, but if you can recompile you can
fix it by replacing line 1179 of treedist.c, which is currently
maxgrp = pow(2,tip_count);
by
maxgrp = 100000;
This is fixed in version 3.69. Versions prior to 3.68 will not have
this problem.
* In Dnacomp, Pars, and Dollop, if the Shimodaira-Hasegawa test is
performed and there are trees perfectly tied with the best tree, the
P values were incorrect (being 0 instead of 1).
* A team from Iowa State University noticed that time was being wasted
in calculations in Dnapenny in the bound calculations. This has now
been remedied and it should be noticeably faster.
* In the molecular likelihood programs, ancestral state probabilities
were being incorrectly calculated for user trees that had internal
multifurcations. This has been corrected.
version 3.68 (August, 2008)
* We received some reports that Dnaml was freezing on some data sets in
the Windows executables. This seems to have been because of incorrect
handling of small increases in the log-likelihood, causing the
algorithm to fall into loops. It was temporarily cured in version 3.67
by changing the compiler optimization level, downwards from -O3 to
-O1. Now the underlying problem of small differences of log-likelihood
has been addressed too, so you should use the new Windows executables
(3.68) to avoid having these problems on Windows systems.
* We found that the .DMG (disk image) archive for Mac OS X contained
executables for the Intel Mac but not universal binaries that would
work on both Intel Mac and PowerPC systems. Oops. We recompiled and
reposted the archives (on 23 August 2007). They should work on both
kinds of systems now.
* We were told that on a Linux computer with a 64-bit Intel Itanium chip
the bootstrapping program Seqboot creates blatantly wrong bootstrap
samples with characters sampled too many times (or none). On a 64-bit
AMD processor the program works fine. The problem is in the random
number function "randum" in phylip.c. It seems to be a problem with
optimization on the GCC compiler. It is cured by dropping the compiler
optimization level from -O3 to -O2.
* In Protdist the program would blow up if it computes a distance
greater than 100.0. This is owing to a subscript error in the code
that writes out the distances, in line 1874 where
else if (d[j][k] < 1000.0)
should have been
else if (d[i][j-1] < 1000.0)
If you have this problem and cannot upgrade to version 3.68 or
recompile the program with this change, and your data comes from
bootstrapping, try omitting just that replicate, or else rerunning
the bootstrapping with a different random number seed (which might not
happen to drop as many of the sites that caused these two sequences to
be so distant).
* When Dnadist is used and the lower-triangular output format is chosen,
the resulting file has headers at the top of columns and is human-
readable but is not machine readable. The (temporary) solution is not
to use this option for the time being.
* In Mac OS X, Drawgram produces some alarming lines of text at the top
of its terminal window when it first runs. These are just scripting
commands that were not erased because we do not clear the screen at
the right moment. The workaround is simply to ignore these commands.
version 3.67 (July, 2007)
* We had our first reports on the behavior of PHYLIP Windows executables
on Windows Vista. The programs work fine. The only thing that did not
work is the self-extraction program that unpacks the archives. For
some reason it did not work on Vista. The work-around was that, after
you got an archive file like phylipwx.exe onto your system, you had to
change the file extension from "exe" to "zip". Then you had to click
on the file. You were presented with options including "Extract all
files". If you chose that the archive was unpacked. The programs would
then work. Although we provided "zip" archive versions of the package,
we have now got a new version of WinZip which is supposed to have a
self-extractor that works on Windows Vista, and it was used to produce
the self-extracting archive since 27 August 2007.
* On Mac OS X systems, if our distributed executables are placed in a
folder whose path contains a name with an internal blank, such as
/Users/ianr/the files/ then the script that causes each of our
programs to run when you click on the corresponding icon does not
work, and there is an error message. This is a scripting error in our
Mac OS X setup, and it was corrected in version 3.67. In the meantime,
if you have this problem, the solution is to put PHYLIP in a folder
whose path does not have any folder that has a blank in its name. In
the above example, all that would be necessary is to rename the folder
the files to the_files
* We are still getting reports of stickiness of the tree, and
occasionally of negative branch lengths, in Dnamlk and Promlk which
do not do as good a job of searching for best trees as they should.
This has turned out to be an issue of nodes getting stuck when they
collide in moving them on the "time" scale. Some major changes were in
the code in the 3.67 release to eliminate this stickiness and give a
good search.
* An error was made in putting together the matrices for the PAM
mutation model in Protdist, Proml, and Promlk. These programs will
give PAM calculations inconsistent with earlier (v3.65 and before)
versions, and with other programs. The matrices were corrected in
version 3.67. This does not affect JTT or PMB models.
* The W (within-species varation) option of CONTRAST uses somewhat
incorrect equations to infer within-species covariances and
phylogenetic covariances. These were corrected in version 3.67.
Anyone severely impacted by the problem in the meantime should contact
me.
* Protdist sometimes results in distances greater than or equal to
100.000. When this happens, the distance can run together with the
previous number in the output file. For example, a distance of 0.31766
followed by one which is 127.43986 might look like this:
"0.31766127.43986". This causes trouble in any program that tries to
use this distance matrix. One symptom of this may be the program
reporting that two distances which are expected to be equal are
unequal -- but then printing them both out, and they appear to be
equal! In this case it would print out a message warning you that
0.31766 was not equal to 0.31766. It is doing so because one of them
is actually seen by it as 0.31766127 and the other 0.31766. In all
future versions, there will be a blank printed between the two
numbers. For the present, use an editor to find them and insert the
blank by hand. If this is difficult, a Sed script (which can be used
on Linux or Unix machines) has been written by Doug Scofield, and is
available from him at: this link. Many thanks to him for this. As you
can see, this problem is the result of us not thinking of what happens
when the distances are big, and the fix in the code is trivial -- just
ensuring that there is at least one blank between successive
distances.
* Contml, with gene frequencies, has a bug in the transformation to
variables that have approximate Brownian motion as their evolutionary
process. This can lead to wierd trees. It might be preferable to go
back to the 3.5c version if you need to use Contml for this. We
believe that this will be correctly fixed in the 3.67 version. If
people can recompile the source code, they replace the function
transformgfs with this one and recompile (you should be able to save
it from your browser using the Save As choice in its File menu.
version 3.66 (August, 2006)
* Program Treedist was found to compute the Branch Score Distance
incorrectly. It will, in most cases, get the branch lengths in
terminal branches incorrect and then be likely to find a nonzero
distance between trees when they are really identical, and incorrect
distances when they are not identical. Alas, there is no workaround to
avoid this. All distances done with this option before version 3.66
should be regarded as incorrect unless all terminal branches have the
same length, or unless the order of species in the tree is the same as
in the first tree in the file. The Symmetric Difference option, which
does not use branch lengths, works properly.
* Program Dnamlk, when run on Linux or Windows systems, sometimes gave
negative branch lengths for some branches on the tree. This is bad.
Although we at first thought that this was a compiler bug, it seems to
be a lack of initialization of some pointers. Program Promlk may have
the same problem, as they share code. If you have this problem you can
work around it by not using the Global menu option when running Dnamlk
(or Promlk). If you need more extensive tree search the J (Jumble)
option may be your best bet.
* On Windows (at least, on Windows xp), our executables for version 3.65
produce output files (outfile) and output tree files (outtree) that
have end-of-line characters that result in their being hard to read on
the Notepad editor. They appear as one big line. If you use the
Wordpad editor, or Microsoft Word itself, the files will be readable.
This is and end-of-line compiler setting we got wrong when compiling
the programs.
* Programs Dnaml and Proml sometimes failed to iterate branch lengths in
trees enough -- this can result in them failing to find as good a tree
as the molecular clock versions Dnamlk and Promlk, a phenomenon that
is not supposed to occur. The problem results from the iteration code
in function makenewv giving up too easily when branch lengths are very
short. The resulting branches get "stuck" at length 0 when they should
not. If you can recompile the programs, the problem can be solved by
the following changes:
o In file phylip.h change the value of the constant iterations to
8 instead of 4.
o In files dnaml.c and proml.c, change function makenewv to
replace
done = fabs(y-yold) < epsilon;
by
done = fabs(y-yold) < 0.1*epsilon;
o In dnaml.c, in function makenewv, also replace*
if (yold < epsilon)
yold = epsilon;
by
if (y < epsilon)
y = epsilon;
We think these fix the problem. Some more thorough fixes are
implemented in the 3.66 code.
* The Mac OS X archives (in .dmg form) appeared at first sight not to
have any executables directory in the package. This is owing to
strange placement of icons once we package the files. The OS X
executables are there -- their folder is just way down the window. Use
the scroll bar to look for them. You should be able to use the
View/Rearrange menus to make the folder icons appear in a more
reasonable place. (Or this can be done once all of the contents of the
.dmg archive are copied out to another folder).
* Programs Dnaml and Proml (but not Dnamlk or Promlk), from version 3.64
on, crashed if the Categories (C) option is used, even if all
categories are given the same rate of change. This unpleasant behavior
does not occur if the menu option for "Speedier but rougher analysis"
is changed to "No, not rough". That slows down the run but allows it
to succeed.
The fix turns out to be that all instances in dnaml.c of calls to
function copynode (or all instances in proml.c of calls to
prot_copynode) that involve an argument lrsaves should have the third
argument be rcategs instead of categs.
* In Seqboot, when menu item J is set to Permute species within
characters it is impossible to change menu item W (character weights).
This is a glitch in the menuing code. If you can change the source
code and recompile, change at line 215 of seqboot.c:
((permute || ild || lockhart)
&& (strchr("ACDEFSJPRXNI%1.20",ch) != NULL)) ||
to be:
(permute && (strchr("ACDEFSJPRWXNI%1.20",ch) != NULL)) ||
((ild || lockhart) && (strchr("ACDEFSJPRXNI%1.20",ch) != NULL)) ||
If you are stuck with our executables and need this feature, you can
also work around it in the following devious way:
1. Set menu item J to some other setting where menu item W appears
in the menu, such as Bootstrap,
2. Change menu item W
3. Then change item J to Permute species within characters
4. Our Makefile for Unix had some problem finding some of the
X-windows libraries on Mac OS X systems on Intel Macs. This
prevented the compilation of Drawtree and Drawgram. You might
have had to use those two programs by using their PowerMac Mac
OS X executables. All the other programs did compile and run
correctly on Intel Macs.
version 3.65 (August, 2005)
* Protpars sometimes gave the result "0 trees found" or else simply
hung and did not complete its run. This was a bug. The program should
always get at least one tree -- if it does not, that is a bug and not
a judgement on your data, provided the data file is in our format!
* Proml and Restml, and maybe some others, seg-faulted when run on
enough multiple data sets, as in bootstrapping. If you have a version
that has this problem and can recompile the programs, here is a fix
for Proml and Restml. In function "inputdata", replace the lines
makeweights();
if ( firstset ) alloclrsaves();
else resetlrsaves();
by
if ( !firstset ) freelrsaves();
makeweights();
alloclrsaves();
and you can also eliminate the now-unnecessary function "restlrsaves".
(Thanks to Jacques Rougemont for this).
version 3.64 (July, 2005)
* Treedist had trouble on Windows systems reading trees. This was due to
problems with the ftell command on CygWin. It has been fixed by having
the files read as binary files.
* Trees with branch lengths compared using Treedist may have incorrect
distances when evaluated as unrooted trees, owing to miscalculation of
branch lengths for the bottommost branches.
* Runs of Seqboot on Mac OS X systems with gene frequencies data have
showed incorrect results -- wrong numbers of loci sampled, for
example. This is due to bad code generated by the Metrowerks
Codewarrior compiler when set to higher levels of optimization (our
source code is OK). We will recompile the program at a lower level of
optimization in the next bug-fixing release. If you can follow our
compiling instructions and have this compiler, you can produce a
correctly working executable. Alternatively you can use the gcc
compiler and use our Unix Makefile to recompile this program (by
typing "make seqboot"). This is quite easy to do and all Mac OS X
releases have the gcc compiler in them -- it only needs to be
installed.
* In runs of Proml, Dnaml or Restml with user trees, if one puts in a
user tree with an internal multifurcation and asks the program to re-
estimate the branch lengths for that tree, the branch lengths in only
two of the furcs will be re-estimated if they already have branch
lengths. This is due to a bug in the function "initrav" causing it to
fail to enter one or more of the subtrees. A workaround until the next
release is as follows: Use Retree to remove all branch lengths on the
tree. The tree's branch lengths will then all be re-estimated when it
is used as a user tree.
* The example output in the Treedist documentation gives distances
computed by version 3.62 or earlier, in which the tree distance is not
square-rooted.
version 3.63 (December, 2004)
* The DNA and protein likelihood programs could have problems with
underflow if very large numbers of sequences were analyzed. Underflow
protection code was needed to make this much less likely to happen.
* A number of programs had the problem that when M (multiple data set)
runs are done, if the data sets differ in the number of characters
from data set to data set, they only allocate enough memory for the
first data set, and then can crash on subsequent, larger, data sets.
For bootstrap and permutation runs this should not be a problem, but
for jackknife runs it might be. One work-around until we fixed this
was to move the data set with the most characters to the front, so
that enough space is allocated. The programs we think had this problem
are: Clique, Dnacomp, Proml, Promlk, Protdist, Dollop, Gendist, Pars,
Restml, and Restdist.
* When the Branch Score distances are computed in program Treedist, the
sum of squares of differences between branches was not square-rooted,
as the documentation web page says it is.
* Fitch and Contml may die when asked to do Jumbling, in some cases.
* Dnaml had inconsistencies in results when branch lengths of a user
tree were estimated, and when the same numbers were provided in the
user tree.
* Trees fed into Contrast could cause trouble if they contained
unifurcations (forks with only one descendant). The program did not
complain about this, as it should have.
* End-of-line characters in input files in certain cases caused trouble
in Mac OS X (for example when the files came over from Windows).
* When printing a rooted tree out in Kitsch, the root was not placed
intermediate between its two decsendants.
* The variable numtrees was sometimes used when still uninitialized in
Pars.
* Restdist had a site-aliasing bookkeeping bug that could lead to
incorrect results.
* Restml would not allow site lengths greater than 8, because an array
was of fixed size when it should have been dynamically allocated.
* The variable name howmany conflicts with predefined names in some
older Sun compilers. It will henceforth be deliberately misspelled to
avoid this.
* With larger data sets being analyzed, Proml, Promlk, Dnaml, and
Dnamlk have had to have underflow protection code installed, as
likelihoods were getting too small.
* Treedist was giving wrong answers when asked to compute all distances
between trees in two files that had unequal numbers of trees. This
was a bookkeeping error.
* The variable scanned was uninitialized in the Drawtree and Drawgram
programs, which could sometimes cause problems.
* The lack of initialization of a variable, delta in Dnadist meant that
different results could be obtained from interactive runs than were
obtained in runs under the control of a command file.
* Dnadist was sometimes stopping when encountering sequences that had
an infinite or indeterminate distance (i.e. when the sequences were
too different or when they had no sites in common), when it should
have printed out "-1" and continued. When it was supposed to print
"-1" in some recent versions of PHYLIP it printed "1.0000" instead.
version 3.62 (September, 2004)
* The ftp link used by our "Get Me PHYLIP" page to fetch the version
3.62 Linux gzip'ed sources and documentation archive was incorrect
until recently (I hadn't updated it to fetch version 3.62). If you had
trouble fetching this archive in version 3.62, please try one more
time. It will work now.
* A number of people have found, with Fitch and with Contml, that
version 3.61 crashes on multiple Jumbling (option J) or on bootstrap
runs. This is fairly serious. It does not happen with versions of
these programs earlier than 3.6 (such as 3.6a3 or 3.573c). This
release fixes these problems.
From pkgsrc-wip, packaged originally by Peter Ibsen Hansen.
GROMACS is a versatile package to perform molecular dynamics,
i.e. simulate the Newtonian equations of motion for systems with
hundreds to millions of particles.
Changes since previous package:
Chemtool-1.6.12 (June 7, 2009)
This release contains another round of fixes for label positioning
and clipping of bonds around labels. The pen color button has been
replaced by a drop-down menu, and a "white" pen for drawing on
colored backgrounds has been added. Chemtool now automatically
resizes its main window on small (netbook) screens, and it can also
be used in an non-interactive mode to create postscript (etc.) output
from previously created chemtool structure files. The Polish
translation has been updated, and a new Bulgarian translation
has been added.
Chemtool-1.6.11 (August 26, 2007)
This release contains numerous fixes for label positioning and
sub/superscript kerning. Bond length and zoom factor are now
stored with the drawing, bond clipping of multiple bonds was
improved and new special key sequences for circled plus and
minus symbols were added. The configuration dialog now lists
gtklp among the supported print commands. Source layout and
build system were reorganized to make addition of translations
easier, and a Portuguese localization file was added.
Chemtool-1.6.10 (April 8th, 2007)
This release adds PNG export, round brackets, text output in
east-european locales and some new templates. Several bugs
related to special character handling in GTK2, screen display
of labels and exporting to EPS and SVG have been fixed. The
configuration dialog has been redone and now includes support
for kprinter, and the labeling shortcuts no longer interfere
with GTK's menu accelerators.
Changes: This release adds a feature that can automatically choose
food quantities when a meal is to have a particular amount of fat,
protein, or carbohydrate. Currently, you can modify a food quantity
from the meal list by typing the food number and a new quantity.
For example, "2 100g" means change food #2 to 100 grams. This
feature allows the user to type "protein", "carb", or "fat" instead
of an explicit new quantity. For example, "2 carb" indicates that
you want the second food's quantity changed so that the meal's
Daily Value for non-fiber carb is satisfied.
* 14.3
Changes: This release modifies the default polyunsaturated fat
reference values.
* 14.2
Changes: This release revises the default fatty acid reference
values.
* 14.1
Changes: This release updates the Omega-3 defaults.
* 14.0
Changes: This release introduces the new USDA Nutrient Database
SR21, and allows current nut installations to have their existing
meal records reinterpreted with the new database.
Shared directories can now be created independently by the pacakges
needing them and will be removed automatically by pkg_delete when empty.
Packages needing empty directories can use the @pkgdir command in PLIST.
Discussed and ok'd in thread starting at
http://mail-index.netbsd.org/tech-pkg/2009/06/30/msg003546.html
on some platforms that lacked shared library support in the past. The
list hasn't been maintained at all and the gain is very limited, so just
get rid of it.
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=...").
patches to add it). Drop pax from the default USE_TOOLS list.
Make bsdtar the default for those places that wanted gtar to extract
long links etc, as bsdtar can be built of the tree.
- assume that Python 2.4 and 2.5 are compatible and allow checking for
fallout.
- remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+
default. Modify the others to deal with the removals.
Pkgsrc changes:
Add DESTDIR support.
Recent changes (cannot available changes from 10.18 to 12.6 anymore).
13.2:
This release makes minor changes to the analysis reset and food suggestion
functions.
13.1:
This release changes some fatty acid defaults to allow more saturated fat when
eating low-carb, and to raise the maximum amount of long-chain Omega-3.
13.0:
This release introduces the new USDA Nutrient Database SR20 and allows current
NUT installations to have their existing meal records reinterpreted with the new
database.
12.7:
This release uses a new food name abbreviation algorithm so that food names are
more informative and less cryptic.
INSTALLATION_DIRS, as well as all occurrences of ${PREFIX}/man with
${PREFIX}/${PKGMANDIR}.
Fixes PR 35265, although I did not use the patch provided therein.
PKGLOCALEDIR and which install their locale files directly under
${PREFIX}/${PKGLOCALEDIR} and sort the PLIST file entries. From now
on, pkgsrc/mk/plist/plist-locale.awk will automatically handle
transforming the PLIST to refer to the correct locale directory.
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
This release fixes a bug i(crash on startup) that was exposed by gcc 4.
It also adds detection of the recently released OpenBabel 2.0 and the ability
to use Openbabel for exporting to foreign file formats. Subscript encoding in
the SVG export was tweaked again to work around current limitations in the SVG
support of Firefox 1.5 and Konqueror 3.x.
of main. Why does it have to be int? Well, not returning anything can
result in a random exit code. Add make(1) as caller and the normal
behaviour of just stopping on the first error and this package has
a very low success rate for building e.g. on DragonFly.
- Fixed several serious bugs related to label rendering and printing
that occured when chemtool was built with GTK 2 instead of GTK 1.2
(see ChangeLog for details)
- SVG export now adds a namespace header as required by current builds
of the firefox browser
- SVG export now uses color values instead of color names for better
SVGT compatibility
- The separation between the lines of multiple bonds is configurable
- The keys of the numeric keypad now create two dots instead of a line
for free electron pairs when the Shift key is pressed
- Two new bond types for drawing filled and unfilled p orbital lobes
- chemtool now checks for fig2sxd (sourceforge.net) and offers to export
to OpenOffice Draw format when it is present.
- rpm packages did not install the dutch locale file.
Chnges 1.6.6:
- Fixed bug in molfile preview that caused an immediate crash in 1.6.5
- Made drawing of wiggly bonds work again
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
10.18:
This release contains a fix for the floating point
exception on NetBSD-2.0/alpha.
10.17:
This release corrects the formatting of the man page and
restores the correct alpha-linolenic acid reference
value, which was too low in the last release.
10.16:
This release fixes a segfault that occurs when analyzing
added and subtracted foods that total zero calories.
10.15:
This release completes the changing of all calculations
to substitute user averages for program constants in the
values of calories per gram of carb, fat, and protein,
and of the percentage of total fat that is fatty acids.
This means that personal options in terms of percentages
and ratios will be more precise.
Arka is a program that serves as a graphical interface for the programs from
the GP package.
Furthermore, it has some interesting functions of it's own. The main scope
of the program is the manipulation and visualisation of DNA / RNA / protein
sequences.
This package comes from pkgsrc-wip; created by <hdp at cs.nmsu.edu> with
several changes by me.
A Sequence Cleanup Program. Lucy is a utility that prepares raw DNA
sequence fragments for sequence assembly,possibly using the TIGR
Assembler. The cleanup process includes quality assessment,
confidence reassurance, vector trimming and vector removal. The
primary advantage of Lucy over other similar utilities is that it is a
fully integrated, stand alone program.
New in 10.13:
This release fixes the incorrect "Analyze Meals" screen header that says
"Record Meals". It fixes the function that guesses recipes of packaged foods,
which worked properly but had a variable and a constant of the same value
reversed so that user modifications to increase the precision would fail.
New in 10.12:
The function that guesses the recipes of packaged foods based on the
nutrition and ingredient statements has been rewritten. A much faster
implementation is achieved by quantizing all the values. This algorithm is a
search through all possible recipes because simultaneous equations do not
work for this problem.
New in 10.11:
This release contains a fix for bad Pumpkin Pie values, specifically, null
"carb/prot/fat" values for foods for which the USDA does not supply this
data.
New in 10.10:
This release fixes a bug in the function that allows foods to be added from
food labels. The carb/protein/fat field was not correct because
calories-per-gram fields were not explicitly set.
New in 10.9:
This release contains a fix for wrong calories-per-gram values when the
program starts because it read a float as an integer from the options file.
New in 10.8:
This release contains many small changes, among them an update of the fatty
acid reference values, a removal of the hard-to-obtain "Alaska Native" foods
as food suggestions, and a closer approximation when protein or carbs are
expressed as a percentage of calories.
New in 10.7:
This release changes how personal options are saved to disk so that personal
options will never be lost across program upgrades. Changes have also been
made to how the program upgrades itself on dual-boot systems, and levels of
the Omega-3 reference values have been modified.
New in 10.6:
This release fixes minor bugs related to the "Carb/Prot/Fat" field. Values
for alcoholic beverages have been corrected. Also, an error was fixed that
led to different fat values based on whether the user input changes to the
protein and carb "Daily Values" in percentages or grams. If the two
operations led to the same number of grams of protein and carbs, there should
have been no difference in the fat value.
New in 10.5:
This release adjusts the Omega-3 default reference values, for which there are
no U.S.A. Daily Values, so that EPA and DHA will be higher and alpha-linolenic
acid a little lower.
New in 10.4:
This release contains two minor design changes to the new feature of the last
release, which automatically chooses a meal analysis period. Always choosing
integer days, the new version picks the day closest to the target rather than
the day before; and allows no period shorter than five days, instead of four.
New in 10.3: don't know.
3.05 - Added -k option to show-coords to only display the best frame for
overlapping PROmer alignments. Added --[no]optimize option to nucmer
and promer to allow alignment score optimization to be turned off, i.e
allow alignments to extend to the ends of sequences rather than
backtracking to optimize the alignment score. Updated docs.
3.06 - Added -F and -h option to mummer. Changed -mumcand option to
-mumreference, but left deprecated -mumcand option available. Added
-maxmatch option to mummer, and changed default behavior of all
applicable programs to -mumreference (nucmer, promer and mummer).
Added -w (screen width) option to show-aligns. Updated documentation
with all of these changes.
3.07 - Added the 'mapview' plotting utility and appropriate documentation.
Fixed origin wrap shadowing bug in show-tiling when using the -c option.
NUCmer and PROmer now convert to absolute paths to avoid ambiguity.
3.08 - Added MUMmer examples web docs which gives brief walkthroughs
3.10 - Now Mac OSX compatible. Added -R option to show-tiling.
3.11 - Fixed bug show-tiling -R option. Added some mapview changes. Fixed
the issue with mummerplot being to faint.
3.12 - Added the --nosimplify option to nucmer for repeat searching. Fixed
a bug in nucmer and promer. Fixed rounding issue in show-coords.
Updated citations.
3.13 - Added -d, -g, -G and -o options to show-coords and updated documentation.
Fixed bug in show-tiling -R
3.14 - Fixed gcc3 compilation bug
3.15 - Fixed --nooptimize in nuc/promer.
While here, enable pkgviews installation.
Changes:
-:- hmmsearch intermittently failed on Swissprot searches, on some
platforms (reports on AMD/Linux; Mac OS/X). (#h25)
-:- hmmpfam memory allocation strategy did not guarantee RAMLIMIT,
and could explode to very large allocations when searching
with large sequences. (#h26)
-:- technical improvements in handing dsq's (digitized sequences);
"bug" has no visible effects, except when compiling on
different platforms. (#h27)
-:- typo fix in P7Forward() recursion; typo may have had minor
effect on calculated scores. (#h28)
-:- hmmalign now includes --outformat and --oneline option for
specifying different output alignment formats than the default
Stockholm.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
CHANGELOG, 12 October 2003
add -X option to glimmer2, to allow orfs extending off ends of
sequence to be scored. Also fix bug affecting -p and -o options
when user chose zero overlap.
* The FASTA format has been added to the list of alignment output
options.
* It is now possible to save the residue ranges (appended after the
sequence names) when saving a specified range of the alignment.
* The efficiency of the neighour-joining algorithm has been improved.
This work was done by Tadashi Koike at the Center for Information
Biology and DNA Data Bank of Japan and FUJITSU Limited.
Some example speedups are given below : (timings on a SPARC64 CPU)
No. of sequences original NJ new NJ
200 0' 12" 0.1"
500 9' 19" 1.4"
1000 XXXX 0' 31"
* ClustalW now returns error codes for some common errors when exiting.
This may be useful for people who run clustalw automatically from within
a script.
Error codes are:
1 bad command line option
2 cannot open sequence file
3 wrong format in sequence file
4 sequence file contains only 1 sequence (for multiple
alignments)
* Alignments can now be saved in Nexus format, for compatibility with
PAUP, MacClade etc. For a description of the Nexus format, see:
Maddison, D. R., D. L. Swofford and W. P. Maddison. 1997.
NEXUS: an extensible file format for systematic information.
Systematic Biology 46:590-621.
* Phylogenetic trees can also be saved in nexus format.
* A ClustalW icon has been designed for MAC and PC systems.
10.1:
This release adds a fix for zero values that display as no data.
10.0:
This release updates the USDA Nutrient Database to version SR17, and allows
current NUT installations to have their existing meal records reinterpreted
with the new database.
9.20:
This release optimizes the new code of the last release, the focus of which
was distinguishing no data from zero in the USDA database.
9.19:
The program now distinguishes between zero values and no data in the USDA
database, and uses this information to produce a new screen that lists foods
high in some nutrient while minimizing some other nutrient.
9.18:
This release contains revisions to the polyunsaturated fatty acid reference
values and how they scale up as fats increase and carbs decrease.
9.17:
This release provides what may be more reasonable or optimal default settings
for fat percentages when the user sets the program for low carb.
9.16:
This release contains bugfixes for a segmentation fault which occurred when
entering a control-D and a monounsaturated fat reference value that was too
high.
9.15:
This release makes serving sizes more consistent among food groups. It adds
functions to change the default serving size, and to sort foods by nutrients
per serving.
9.14:
This release adds support for an optional database subdirectory, allowing the
user to easily maintain multiple databases, for multiple family members, for
instance. It also adds display of non-fiber carbohydrate grams ("net carbs")
on the main analysis screen.
9.13:
The program now allows commercial foods that have a nutrition label and an
ordered ingredients statement to be added to the food database. An
approximation to a food's recipe is found that best fits the criteria and the
recipe is analyzed to provide information about the additional nutrients not
stated on the nutrition label.
9.12:
[unknown]
Update distinfo for new archive. Only minor bug fixes, no version change.
For a detailed diff, see:
ftp://ftp.netbsd.org/pub/NetBSD/misc/ben/profit-2004-08-14.txt
This addresses PR#26656 from Georg Schwarz.
New in 9.11:
Because the program uses the approximation of 4 calories per gram
for carbohydrate and protein to analyze meals according to the
"Daily Value" -- although real food has various values for calories
per gram -- the program now refigures fat percentage values at each
analysis so that when calories, carbs, and protein are each at
exactly 100%, fat will be also.
New in 9.10:
This release fixes a buffer overflow in the food selection function
which caused the program to not find certain foods even though they
existed in the database.
New in 9.9:
A bug has been fixed in which during food selection, the program
lost the value of the food name key. Also, some of the program's
reference values for the essential fatty acids have been modified.
New in 9.8:
The program now defaults to either grams or ounces, depending on
the weight unit the user enters to specify servings. A bug in
handling customary meal names that are too long has been fixed.
New in 9.7:
The program computes essential fatty acid reference values based
on the user's diet. Prior releases aimed toward a particular balance
of Omega-6 and Omega-3. This release allows the user to specify
the balance between Omega-6 and Omega-3 without having to determine
the amount of the individual fatty acids.
New in 9.6:
The program is now capable of understanding food names in simple
English, such as "fried chicken" and "mashed potatoes." This is
accomplished by including the list of abbreviations the USDA uses
and by successively searching for each tokenized term, whatever
the order in the USDA name.
9.5:
The last release introduced a bug when adding customary meals to
regular meals. The program now adds the foods without the additional
prompt screen.
9.4:
This release changes the method of searching for foods to a substring
search. The narrowing-down of food categories to a unique food is
the same as in prior releases.
This release fixes a bug in the graphs where the "Daily Value" was
such a small percentage of the values graphed that the DV line
indicator exceeded the graph width.
gcc3. While here, update to version 2.12 (previous version was erraneously
named 2.1, when it should have been 2.10) which is the only distfile
available on the ftp site.
Changelog seems to say:
- Fix bug on long-orfs.cc to avoid occasional array out-of-bounds
error (detected on Mac OS X).
9.2:
The upper limit of the polyunsaturated reference value for linoleic
acid has been reduced to 4% of calories, while that for alpha
linolenic acid has been raised to 2%. An internal constant for the
percentage of total fat that is fatty acids has been replaced by
a function that figures it for each analysis.
9.1:
The program is no longer limited to three meals a day, and can now
be set for 1 to 19 meals per day. A list of the meals not yet
recorded for a selected day is displayed as a mnemonic during the
"Record Meals" function.
brook at biology dot nmsu dot edu and his team at NMSU.
XYLEM is a package of tools designed to exploit the Unix environment to enable
the user to identify, extract and manipulate data from major databases such as
GenBank, EMBL and PIR.
brook at biology dot nmsu dot edu and his team at NMSU.
Glimmer (Gene Locator and Interpolated Markov Modeler) is a system for finding
genes in microbial DNA, especially the genomes of bacteria and archaea.
Glimmer uses interpolated Markov models (IMMs) to identify the coding regions
and distinguish them from noncoding DNA. The IMM approach uses a combination
of Markov models from 1st through 8th-order, weighting each model according to
its predictive power.
brook at biology dot nmsu dot edu and his team at NMSU.
GeneSplicer is a fast, flexible system for detecting splice sites in the
genomic DNA of various eukaryotes. The system has been trained and tested
successfully on Plasmodium falciparum (malaria), Arabidopsis thaliana, human,
Drosophila, and rice.
brook at biology dot nmsu dot edu and his team at NMSU.
FLUCTUATE fits the model which has a single population which has been
growing (or shrinking) according to an exponential growth law. It
estimates 4Nu and g, where N is the effective population size, u is
the neutral mutation rate per site, and g is the growth rate of the
population.
brook at biology dot nmsu dot edu and his team at NMSU.
COALESCE fits the model which has a single population of constant size, and
estimates 4Nu, where N is the effective population size and u is the neutral
mutation rate per site.
