ViewVC Help
View Directory | Revision Log | Download Tarball | View Changeset | Root Listing
root/owl/tags/owl-for-eppic-2.0.2
r1704
File Last Change
 ../
jars/ 1664 (4 years ago) by jmduarteg: Tagging for eppic release 2.0.2 - bug fix: null pointer in pdb file parsing when no TER records present or misplaced - many improvements in SpaceGroup and its testing - operators can now be classified into their types, including calculation of screw directions - bug fix: the axis vectors were wrongly calculated for some operators of some space groups, e.g. in H 3 2 or P 32 2 1 - bug fix in jaligner: sequences longer than 32768 characters were not aligning correctly when the match was occurring after character 32768. We fixed it ourselves in the jaligner source and repackaged the jar into owl. The jaligner developer has fixed it in git.
modelit/ 1664 (4 years ago) by jmduarteg: Tagging for eppic release 2.0.2 - bug fix: null pointer in pdb file parsing when no TER records present or misplaced - many improvements in SpaceGroup and its testing - operators can now be classified into their types, including calculation of screw directions - bug fix: the axis vectors were wrongly calculated for some operators of some space groups, e.g. in H 3 2 or P 32 2 1 - bug fix in jaligner: sequences longer than 32768 characters were not aligning correctly when the match was occurring after character 32768. We fixed it ourselves in the jaligner source and repackaged the jar into owl. The jaligner developer has fixed it in git.
reconstruct/ 1664 (4 years ago) by jmduarteg: Tagging for eppic release 2.0.2 - bug fix: null pointer in pdb file parsing when no TER records present or misplaced - many improvements in SpaceGroup and its testing - operators can now be classified into their types, including calculation of screw directions - bug fix: the axis vectors were wrongly calculated for some operators of some space groups, e.g. in H 3 2 or P 32 2 1 - bug fix in jaligner: sequences longer than 32768 characters were not aligning correctly when the match was occurring after character 32768. We fixed it ourselves in the jaligner source and repackaged the jar into owl. The jaligner developer has fixed it in git.
scripts/ 1664 (4 years ago) by jmduarteg: Tagging for eppic release 2.0.2 - bug fix: null pointer in pdb file parsing when no TER records present or misplaced - many improvements in SpaceGroup and its testing - operators can now be classified into their types, including calculation of screw directions - bug fix: the axis vectors were wrongly calculated for some operators of some space groups, e.g. in H 3 2 or P 32 2 1 - bug fix in jaligner: sequences longer than 32768 characters were not aligning correctly when the match was occurring after character 32768. We fixed it ourselves in the jaligner source and repackaged the jar into owl. The jaligner developer has fixed it in git.
src/ 1664 (4 years ago) by jmduarteg: Tagging for eppic release 2.0.2 - bug fix: null pointer in pdb file parsing when no TER records present or misplaced - many improvements in SpaceGroup and its testing - operators can now be classified into their types, including calculation of screw directions - bug fix: the axis vectors were wrongly calculated for some operators of some space groups, e.g. in H 3 2 or P 32 2 1 - bug fix in jaligner: sequences longer than 32768 characters were not aligning correctly when the match was occurring after character 32768. We fixed it ourselves in the jaligner source and repackaged the jar into owl. The jaligner developer has fixed it in git.
.classpath 1664 (4 years ago) by jmduarteg: Tagging for eppic release 2.0.2 - bug fix: null pointer in pdb file parsing when no TER records present or misplaced - many improvements in SpaceGroup and its testing - operators can now be classified into their types, including calculation of screw directions - bug fix: the axis vectors were wrongly calculated for some operators of some space groups, e.g. in H 3 2 or P 32 2 1 - bug fix in jaligner: sequences longer than 32768 characters were not aligning correctly when the match was occurring after character 32768. We fixed it ourselves in the jaligner source and repackaged the jar into owl. The jaligner developer has fixed it in git.
.project 1664 (4 years ago) by jmduarteg: Tagging for eppic release 2.0.2 - bug fix: null pointer in pdb file parsing when no TER records present or misplaced - many improvements in SpaceGroup and its testing - operators can now be classified into their types, including calculation of screw directions - bug fix: the axis vectors were wrongly calculated for some operators of some space groups, e.g. in H 3 2 or P 32 2 1 - bug fix in jaligner: sequences longer than 32768 characters were not aligning correctly when the match was occurring after character 32768. We fixed it ourselves in the jaligner source and repackaged the jar into owl. The jaligner developer has fixed it in git.
LICENSE 1664 (4 years ago) by jmduarteg: Tagging for eppic release 2.0.2 - bug fix: null pointer in pdb file parsing when no TER records present or misplaced - many improvements in SpaceGroup and its testing - operators can now be classified into their types, including calculation of screw directions - bug fix: the axis vectors were wrongly calculated for some operators of some space groups, e.g. in H 3 2 or P 32 2 1 - bug fix in jaligner: sequences longer than 32768 characters were not aligning correctly when the match was occurring after character 32768. We fixed it ourselves in the jaligner source and repackaged the jar into owl. The jaligner developer has fixed it in git.
build.xml 1664 (4 years ago) by jmduarteg: Tagging for eppic release 2.0.2 - bug fix: null pointer in pdb file parsing when no TER records present or misplaced - many improvements in SpaceGroup and its testing - operators can now be classified into their types, including calculation of screw directions - bug fix: the axis vectors were wrongly calculated for some operators of some space groups, e.g. in H 3 2 or P 32 2 1 - bug fix in jaligner: sequences longer than 32768 characters were not aligning correctly when the match was occurring after character 32768. We fixed it ourselves in the jaligner source and repackaged the jar into owl. The jaligner developer has fixed it in git.
gpl.txt 1664 (4 years ago) by jmduarteg: Tagging for eppic release 2.0.2 - bug fix: null pointer in pdb file parsing when no TER records present or misplaced - many improvements in SpaceGroup and its testing - operators can now be classified into their types, including calculation of screw directions - bug fix: the axis vectors were wrongly calculated for some operators of some space groups, e.g. in H 3 2 or P 32 2 1 - bug fix in jaligner: sequences longer than 32768 characters were not aligning correctly when the match was occurring after character 32768. We fixed it ourselves in the jaligner source and repackaged the jar into owl. The jaligner developer has fixed it in git.
         5 files shown

Properties

Name Value
svn:ignore .classpath .project .settings build