loos-users Mailing List for LOOS
Analyze molecular simulation data
Brought to you by:
alan_grossfield,
drtromo
You can subscribe to this list here.
| 2014 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(17) |
Oct
|
Nov
|
Dec
(6) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2015 |
Jan
(3) |
Feb
|
Mar
|
Apr
(16) |
May
(4) |
Jun
(2) |
Jul
(8) |
Aug
(8) |
Sep
(8) |
Oct
|
Nov
|
Dec
(12) |
| 2016 |
Jan
|
Feb
|
Mar
(8) |
Apr
(2) |
May
(44) |
Jun
(16) |
Jul
(2) |
Aug
(7) |
Sep
(4) |
Oct
|
Nov
(5) |
Dec
(16) |
| 2017 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
(6) |
Nov
|
Dec
(9) |
| 2018 |
Jan
(12) |
Feb
(5) |
Mar
|
Apr
(7) |
May
(6) |
Jun
|
Jul
(2) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
(1) |
Feb
(4) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: LOOS <loo...@gm...> - 2019-10-22 20:09:20
|
Hi Zeineb, Thanks for providing so much detail — that will help me try to help you. > On Oct 22, 2019, at 2:40 PM, Zeineb Si Chaib <z.s...@fz...> wrote: > > Dear LOOS users, > > I have coarse-grained trajectories with Martini FF of a membrane protein in an explicit membrane (POPC, POPE, CHOL) and water + ions environment. > > I would like to calculate the local density of the different lipids around my protein. The final result should be a 2D time-averaged density map like the one done in this article (Figure 2): https://www.ncbi.nlm.nih.gov/pubmed/24158802 <https://www.ncbi.nlm.nih.gov/pubmed/24158802>. The Authors also used LOOS to perform this analysis. > > Question > 1- I read the LOOS documentation and I think that membrane_map is a suitable tool for this. Someone to confirm it? :) > > This tool assumes that the bilayer normal is the z-axis and that the bilayer center is at z=0. In order to get this I post-processed my trajectory with Gromacs (I am used to it) using the following commands: > > A) gmx trjconv -s md.tpr -f md.xtc -o md_PBCnojump.xtc -pbc nojump > B) gmx trjconv -s md.tpr -f md_PBCnojump.xtc -o md_PBCnojump_center.xtc -center > #Group for centering = protein > C) gmx trjconv -s md.tpr -f md_PBCnojump_center.xtc -o md_PBCnojump_center_pbcmol_compact.xtc -pbc mol -ur compact > This looks ok, but I’m only moderately competent with gromacs so I’m not sure. > The obtained trajectory seems good: protein (dimer) centered in the box and the bilayer normal is the z-axis. However, the center is not at z=0. > > I looked in LOOS tools and it seems that merge-traj can be used to center at z=o. This code will work best if the system has connectivity information thus I used gmxdump2pdb.pl to get a PSF file for my system: > > gmx dump -s md.tpr | gmxdump2pdb.pl fake_system > > The command line generated one PDB and one PSF file but with some Warnings : > Missing atom count in topology so inferring number of atoms in segment Protein_A at gmxdump2pdb.pl line 594, <> line 63555. > Missing atom count in topology so inferring number of atoms in segment Protein_B at gmxdump2pdb.pl line 594, <> line 63555. > Missing atom count in topology so inferring number of atoms in segment POPC at gmxdump2pdb.pl line 594, <> line 63555. > Missing atom count in topology so inferring number of atoms in segment POPE at gmxdump2pdb.pl line 594, <> line 63555. > Missing atom count in topology so inferring number of atoms in segment CHOL at gmxdump2pdb.pl line 594, <> line 63555. > Missing atom count in topology so inferring number of atoms in segment POPC at gmxdump2pdb.pl line 594, <> line 63555. > Missing atom count in topology so inferring number of atoms in segment POPE at gmxdump2pdb.pl line 594, <> line 63555. > Missing atom count in topology so inferring number of atoms in segment CHOL at gmxdump2pdb.pl line 594, <> line 63555. > Missing atom count in topology so inferring number of atoms in segment W at gmxdump2pdb.pl line 594, <> line 63555. > Missing atom count in topology so inferring number of atoms in segment NA at gmxdump2pdb.pl line 594, <> line 63555. > Missing atom count in topology so inferring number of atoms in segment CL at gmxdump2pdb.pl line 594, <> line 63555. This looks ok. If you look at the resulting PSF and PDB, are they ok? > > I used merge-traj tool as follow to center at z=0: > > merge-traj --z-centering-selection ‘resname=="POPC POPE CHOL"’ fake_system.psf output_traj.dcd Traj.dcd The z-centering-selection is wrong — nothing will be selected. You want something like ‘(resname==“POPC”) || (resname == “POPE”) || (resname == “CHOL”)’ You could have done the whole recentering thing in one shot by also supplying an —xy-centering-selection option, eg —xy-centering-selection ’segname =~ “Protein_”' > > The problem that I got is that I can’t open the trajectory (dcd + psf files) because it seems that the latter doesn’t contain all the connectivity information (bonds, angles, and dihedrals are missing). Can you send me the warning or error message you’re getting here? I don’t know what this means. Also, what happens if you run trajinfo fake_system.psf output_traj.dcd > I tried to replace the psf file in the merge-traj command line with the PDB file but the same problem: I can’t read the output trajectory and I think that this tool only generates dcd format output. > > Question > 2- Am I using merge-traj correctly? (The aim is just to center at z=0 since all the rest seems OK.) The selection string was wrong, but otherwise it looks ook. > 3- How can I counter this problem? Is there any other tool that I can use in order to preprocess the trajectory before using membrane-map? > > Next, I tried to do some tests with membrane-map just to see how this tool works. For example: in order to calculate the density of CHOL molecules around the protein I was using it as follow : > > membrane_map --xmin -130 --xmax 130 --ymin -130 --ymax 130 --xbins 130 --ybins 130 --upper-only Traj_frame0.pdb Traj_concatenaed.pdb --calc density 'resname == "CHOL"' 'name== "BB”’ > output.xvg The align selection isn’t what you want, I don’t think. Right now, you’re aligning on the cholesterols, and measuring the density of “BB”. Aligning on the cholesterols doesn’t make much sense, because they’re moving around. I think you want to align on the protein, so the cholesterol selection should be replaced with ’segname =~ “Protein_”’ which would align each frame against the protein segments from the first frame. I’m not sure what atom BB is, but you’ll get the density of it in each pixel. > > The output was: > # Found 1 matching molecules > # X Y > Value(s) > -130 -130 > 0 > -130 -128 > 0 > > Questions > 4- Correct me if I am wrong, please: xmin, xmax, ymin and ymax are the dimensions of the 2D grid and consequently they should correspond to the dimensions of the box of the simulation? Yes, this is correct. > 5- According to what on what I should choose the values for xbin and ybin? any specifications for coarse-grained system? Basically, it’s a tradeoff between a rougher grid with less noise and a finer grid with more. 2x2 Ang is pretty reasonable to start. Luckily, it runs fast so you can try more than 1 grid size. > 6- The output file starts with "# Found 1 matching molecules”. The matching molecule corresponds to the “align-selection”? That says it found 1 molecule matching your target selection — the BB atoms. > 7- The output file has 3 columns. X and Y columns are points in the 2D grid and the 3rd column should correspond to the time-average density of Cholesterol molecules at this coordinate. Is that correct? > I suppose that 0 values that I am getting are because my trajectory is not centered at z=0 so of course, this output is not significant. It’ll actually be the density of atom BB. > > I am sorry for all these questions. I am a new user of LOOS and I want to check if my understanding is correct and to be sure that I am using the tools in the correct way. > No problem, I’m happy to help. Our terminology is a little foreign, because we have to be useable to multiple packages, and they don’t refer to things the same way. Going forward, though, you might want to either raise an issue on GitHub, or email loo...@gm... – we’ve migrated off SourceForge and are discouraging use of the mailing lists. Hope this helps — if not, write back and I’ll keep trying to help. Cheers, Alan ________________________________ Dr. Alan Grossfield Associate Professor Department of Biochemistry and Biophysics University of Rochester Medical Center 610 Elmwood Ave, Box 712 Rochester, NY 14642 Phone: 585 276 4193 http://membrane.urmc.rochester.edu https://orcid.org/0000-0002-5877-2789 |
|
From: Zeineb Si C. <z.s...@fz...> - 2019-10-22 18:41:20
|
Dear LOOS users, I have coarse-grained trajectories with Martini FF of a membrane protein in an explicit membrane (POPC, POPE, CHOL) and water + ions environment. I would like to calculate the local density of the different lipids around my protein. The final result should be a 2D time-averaged density map like the one done in this article (Figure 2): https://www.ncbi.nlm.nih.gov/pubmed/24158802. The Authors also used LOOS to perform this analysis. Question 1- I read the LOOS documentation and I think that membrane_map is a suitable tool for this. Someone to confirm it? :) This tool assumes that the bilayer normal is the z-axis and that the bilayer center is at z=0. In order to get this I post-processed my trajectory with Gromacs (I am used to it) using the following commands: A) gmx trjconv -s md.tpr -f md.xtc -o md_PBCnojump.xtc -pbc nojump B) gmx trjconv -s md.tpr -f md_PBCnojump.xtc -o md_PBCnojump_center.xtc -center #Group for centering = protein C) gmx trjconv -s md.tpr -f md_PBCnojump_center.xtc -o md_PBCnojump_center_pbcmol_compact.xtc -pbc mol -ur compact The obtained trajectory seems good: protein (dimer) centered in the box and the bilayer normal is the z-axis. However, the center is not at z=0. I looked in LOOS tools and it seems that merge-traj can be used to center at z=o. This code will work best if the system has connectivity information thus I used gmxdump2pdb.pl to get a PSF file for my system: gmx dump -s md.tpr | gmxdump2pdb.pl fake_system The command line generated one PDB and one PSF file but with some Warnings : Missing atom count in topology so inferring number of atoms in segment Protein_A at gmxdump2pdb.pl line 594, <> line 63555. Missing atom count in topology so inferring number of atoms in segment Protein_B at gmxdump2pdb.pl line 594, <> line 63555. Missing atom count in topology so inferring number of atoms in segment POPC at gmxdump2pdb.pl line 594, <> line 63555. Missing atom count in topology so inferring number of atoms in segment POPE at gmxdump2pdb.pl line 594, <> line 63555. Missing atom count in topology so inferring number of atoms in segment CHOL at gmxdump2pdb.pl line 594, <> line 63555. Missing atom count in topology so inferring number of atoms in segment POPC at gmxdump2pdb.pl line 594, <> line 63555. Missing atom count in topology so inferring number of atoms in segment POPE at gmxdump2pdb.pl line 594, <> line 63555. Missing atom count in topology so inferring number of atoms in segment CHOL at gmxdump2pdb.pl line 594, <> line 63555. Missing atom count in topology so inferring number of atoms in segment W at gmxdump2pdb.pl line 594, <> line 63555. Missing atom count in topology so inferring number of atoms in segment NA at gmxdump2pdb.pl line 594, <> line 63555. Missing atom count in topology so inferring number of atoms in segment CL at gmxdump2pdb.pl line 594, <> line 63555. I used merge-traj tool as follow to center at z=0: merge-traj --z-centering-selection ‘resname=="POPC POPE CHOL"’ fake_system.psf output_traj.dcd Traj.dcd The problem that I got is that I can’t open the trajectory (dcd + psf files) because it seems that the latter doesn’t contain all the connectivity information (bonds, angles, and dihedrals are missing). I tried to replace the psf file in the merge-traj command line with the PDB file but the same problem: I can’t read the output trajectory and I think that this tool only generates dcd format output. Question 2- Am I using merge-traj correctly? (The aim is just to center at z=0 since all the rest seems OK.) 3- How can I counter this problem? Is there any other tool that I can use in order to preprocess the trajectory before using membrane-map? Next, I tried to do some tests with membrane-map just to see how this tool works. For example: in order to calculate the density of CHOL molecules around the protein I was using it as follow : membrane_map --xmin -130 --xmax 130 --ymin -130 --ymax 130 --xbins 130 --ybins 130 --upper-only Traj_frame0.pdb Traj_concatenaed.pdb --calc density 'resname == "CHOL"' 'name== "BB”’ > output.xvg The output was: # Found 1 matching molecules # X Y Value(s) -130 -130 0 -130 -128 0 Questions 4- Correct me if I am wrong, please: xmin, xmax, ymin and ymax are the dimensions of the 2D grid and consequently they should correspond to the dimensions of the box of the simulation? 5- According to what on what I should choose the values for xbin and ybin? any specifications for coarse-grained system? 6- The output file starts with "# Found 1 matching molecules”. The matching molecule corresponds to the “align-selection”? 7- The output file has 3 columns. X and Y columns are points in the 2D grid and the 3rd column should correspond to the time-average density of Cholesterol molecules at this coordinate. Is that correct? I suppose that 0 values that I am getting are because my trajectory is not centered at z=0 so of course, this output is not significant. I am sorry for all these questions. I am a new user of LOOS and I want to check if my understanding is correct and to be sure that I am using the tools in the correct way. Thank you in advance for your help. Best, ----- Zeineb SI CHAIB IAS-5 / INM-9: Computational Biomedicine - Institute for Advanced Simulation (IAS)/Institute of Neuroscience and Medicine (INM) Forschungszentrum Jülich D-52425 Jülich, Germany ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Volker Rieke Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ |
|
From: Eric S. <sef...@gm...> - 2019-03-01 17:51:24
|
Dear LOOS users, I have question about application of the packing score tool and interpretation of the results. I'm analyzing a MARTINI simulation with 16 membrane proteins embedded in a POPE:POPG membrane doped with hopanoids (a cholesterol analog). When I run the packing_score analysis: packing_score --skip 0 --normalize --sel1 'id >= 1837 && id <= 2448' --sel2 'resname == "HBHT"' system_fake.psf recenter.dcd > pack4_scoreBT2.txt The output looks like this: 0 1.00971e-08 1 9.60765e-09 2 1.00561e-08 3 9.95897e-09 4 9.91984e-09 5 9.28185e-09 6 9.66481e-09 Which is consistent with what I would expect, based on the PNAS 2006 paper that this was first used (Fig. 1). However, when I combine all of my data, the probability of my packing score drops off as it approaches zero [image: image.png] This doesn't make sense to me, as the packing score from the PNAS paper clearly looks like it behaves similar to a CDF, with max probability occurring as you approach zero. Have I improperly used the packing_score tool, or am I reading too much into my dataset? Thanks! Eric Sefah |
|
From: LOOS <loo...@gm...> - 2019-02-27 21:12:27
|
Hi LOOSers, We just released LOOS 3.0.0 on GitHub (https://github.com/GrossfieldLab/loos <https://github.com/GrossfieldLab/loos>). This is a big change, including a switch from python 2.7 to python 3.x, support for building in a Conda environment, a new reweighting facility for computing weighted averages in LOOS, and a bunch of small fixes and improvements as well. As part of this change, we’re also migrating away from Sourceforge as a platform. The Sourceforge page now redirects to github, so the only remnant of sourceforge is these mailing lists. Accordingly, we now recommend that the best way to request help, suggest a new feature, etc, is to raise an issue on Github. Also, if you want to be notified of new releases, etc, please follow LOOS on Github. For those of you attending the Biophysical Society meeting, please stop by our poster — it’s on Sunday, board B470. Sincerely, Alan and Tod ________________________________ Dr. Alan Grossfield Associate Professor Department of Biochemistry and Biophysics University of Rochester Medical Center 610 Elmwood Ave, Box 712 Rochester, NY 14642 Phone: 585 276 4193 http://membrane.urmc.rochester.edu https://orcid.org/0000-0002-5877-2789 |
|
From: Yasser A. H. <yas...@ch...> - 2019-02-13 16:03:17
|
Hello, thank very much for your reply. > Also, you’ll need to post-process trajectories from gromacs anyway, > because of its brain-dead insistence on breaking molecules across the > periodic boundaries. Either merge-traj or subsetter can do this for > you. We made the design decision to assume you’ll post-process the > trajectories once they’re in a sane state, rather than including the > logic to fix broken molecules (and center appropriately, etc) in every > tool. I’m sorry if that’s inconvenient for your specific workflow. Got it. I already have my gromacs trajectories pre-processed (in gromacs) where the protein is centered and molecules are not broken (with flag -pbc mol in gmx trjconv). I will then re-process the trajectories with merge-traj, with flags --fix-imaging and --z-centering-selection. Best regards Yasser On 13.02.2019 16:43, LOOS wrote: > Hi, > > That’s not going to work — even if you manually select all lower > leaflet lipids, the code will separate them into upper and lower based > on their Z position. > > Also, you’ll need to post-process trajectories from gromacs anyway, > because of its brain-dead insistence on breaking molecules across the > periodic boundaries. Either merge-traj or subsetter can do this for > you. We made the design decision to assume you’ll post-process the > trajectories once they’re in a sane state, rather than including the > logic to fix broken molecules (and center appropriately, etc) in every > tool. I’m sorry if that’s inconvenient for your specific workflow. > > Dr. Alan Grossfield > Department of Biochemistry and Biophysics > University of Rochester Medical Center > > On Feb 13, 2019, at 7:58 AM, Yasser Almeida Hernández > <yas...@ch... > <mailto:yas...@ch...>> wrote: > >> Hello, >> >> I have some CG simulations of a membrane protein in a model bilayer >> with several lipids and I want to analyze the radial density function >> of each lipid using the xy_rdf tool (as in Fig 5.2 of >> https://link.springer.com/chapter/10.1007%2F978-94-007-7423-0_5). The >> runs were performed with GROMACS. >> >> As stated in the documentation it is recommended first to use the >> merge_trj tool to center the system along the Z axis, necessary for >> the leaflets identification. I want to avoid that manipulation and >> instead, I defined the lipids leaflet explicitly in the second >> selection of the xy_rdf tool, as following: >> >> > xy_rdf --modeltype gro --trajtype xtc system.gro traj.xtc 'name == >> "BB"' 'resid >= 277 && resid <= 474 && resname == "DOPG" && name == >> "PO4"' 0 60 300 > loos_bottom_xy_rdf_DOPG.dat >> >> The "BB" selection correspond to the backbone CG beads of the >> protein. The second selection correspond to the PO4 beads of the DOPG >> lipids in the lower leaflet. >> >> The bilayer is composed by PE- and PG based lipids at a 70.5% / 27% >> ratio. >> >> For comparison I obtained the RDFs using the GROMACS's gmx rdf tool >> (with and without the -xy flag). The curves with xy_rdf are weird, >> they go to 0, when is expected to converge to 1. >> >> Any thoughts? >> >> Thanks in advance. >> >> Yasser >> >> -- >> Yasser Almeida Hernández >> PhD student >> Institute of Biochemistry and Molecular Biology >> Department of Chemistry >> University of Hamburg >> Martin-Luther-King-Platz 6 >> 20146 Hamburg >> Germany >> +49 40 42838 2845 >> yas...@ch... >> office: Grindelallee 117, room 250c >> <GROMACS_3D_2D_LOOS.jpg> >> _______________________________________________ >> Loos-users mailing list >> Loo...@li... >> <mailto:Loo...@li...> >> https://lists.sourceforge.net/lists/listinfo/loos-users -- Yasser Almeida Hernández PhD student Institute of Biochemistry and Molecular Biology Department of Chemistry University of Hamburg Martin-Luther-King-Platz 6 20146 Hamburg Germany +49 40 42838 2845 yas...@ch... office: Grindelallee 117, room 250c |
|
From: LOOS <loo...@gm...> - 2019-02-13 15:43:41
|
Hi, That’s not going to work — even if you manually select all lower leaflet lipids, the code will separate them into upper and lower based on their Z position. Also, you’ll need to post-process trajectories from gromacs anyway, because of its brain-dead insistence on breaking molecules across the periodic boundaries. Either merge-traj or subsetter can do this for you. We made the design decision to assume you’ll post-process the trajectories once they’re in a sane state, rather than including the logic to fix broken molecules (and center appropriately, etc) in every tool. I’m sorry if that’s inconvenient for your specific workflow. Dr. Alan Grossfield Department of Biochemistry and Biophysics University of Rochester Medical Center > On Feb 13, 2019, at 7:58 AM, Yasser Almeida Hernández <yas...@ch...> wrote: > > Hello, > > I have some CG simulations of a membrane protein in a model bilayer with several lipids and I want to analyze the radial density function of each lipid using the xy_rdf tool (as in Fig 5.2 of https://link.springer.com/chapter/10.1007%2F978-94-007-7423-0_5). The runs were performed with GROMACS. > > As stated in the documentation it is recommended first to use the merge_trj tool to center the system along the Z axis, necessary for the leaflets identification. I want to avoid that manipulation and instead, I defined the lipids leaflet explicitly in the second selection of the xy_rdf tool, as following: > > > xy_rdf --modeltype gro --trajtype xtc system.gro traj.xtc 'name == "BB"' 'resid >= 277 && resid <= 474 && resname == "DOPG" && name == "PO4"' 0 60 300 > loos_bottom_xy_rdf_DOPG.dat > > The "BB" selection correspond to the backbone CG beads of the protein. The second selection correspond to the PO4 beads of the DOPG lipids in the lower leaflet. > > The bilayer is composed by PE- and PG based lipids at a 70.5% / 27% ratio. > > For comparison I obtained the RDFs using the GROMACS's gmx rdf tool (with and without the -xy flag). The curves with xy_rdf are weird, they go to 0, when is expected to converge to 1. > > Any thoughts? > > Thanks in advance. > > Yasser > > -- > Yasser Almeida Hernández > PhD student > Institute of Biochemistry and Molecular Biology > Department of Chemistry > University of Hamburg > Martin-Luther-King-Platz 6 > 20146 Hamburg > Germany > +49 40 42838 2845 > yas...@ch... > office: Grindelallee 117, room 250c > <GROMACS_3D_2D_LOOS.jpg> > _______________________________________________ > Loos-users mailing list > Loo...@li... > https://lists.sourceforge.net/lists/listinfo/loos-users |
|
From: Yasser A. H. <yas...@ch...> - 2019-02-13 13:14:10
|
Hello, I have some CG simulations of a membrane protein in a model bilayer with several lipids and I want to analyze the radial density function of each lipid using the xy_rdf tool (as in Fig 5.2 of https://link.springer.com/chapter/10.1007%2F978-94-007-7423-0_5). The runs were performed with GROMACS. As stated in the documentation it is recommended first to use the merge_trj tool to center the system along the Z axis, necessary for the leaflets identification. I want to avoid that manipulation and instead, I defined the lipids leaflet explicitly in the second selection of the xy_rdf tool, as following: > xy_rdf --modeltype gro --trajtype xtc system.gro traj.xtc 'name == "BB"' 'resid >= 277 && resid <= 474 && resname == "DOPG" && name == "PO4"' 0 60 300 > loos_bottom_xy_rdf_DOPG.dat The "BB" selection correspond to the backbone CG beads of the protein. The second selection correspond to the PO4 beads of the DOPG lipids in the lower leaflet. The bilayer is composed by PE- and PG based lipids at a 70.5% / 27% ratio. For comparison I obtained the RDFs using the GROMACS's gmx rdf tool (with and without the -xy flag). The curves with xy_rdf are weird, they go to 0, when is expected to converge to 1. Any thoughts? Thanks in advance. Yasser -- Yasser Almeida Hernández PhD student Institute of Biochemistry and Molecular Biology Department of Chemistry University of Hamburg Martin-Luther-King-Platz 6 20146 Hamburg Germany +49 40 42838 2845 yas...@ch... office: Grindelallee 117, room 250c |
|
From: Blake M. <me...@gm...> - 2019-01-28 23:14:11
|
Hello, I'm running Debian 9 with kernel 4.19.0-1, libboost version 1.67, gcc/g++/gfortran 8.2.0, and scons 3.0.1. After compiling with scons PREFIX=/usr/local/src/loos-2.3.2 install, I get a compile error: g++ -o Tools/rmsds Tools/rmsds.o -L. -Lsrc -L/usr/lib libloos.so -lnetcdf -lboost_regex -lboost_system -lboost_program_options -lboost_thread -llapack -lf77blas -lcblas -latlas /usr/bin/ld: Tools/rmsds.o: undefined reference to symbol 'pthread_condattr_setclock@@GLIBC_2.3.3' /usr/bin/ld: //lib/x86_64-linux-gnu/libpthread.so.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status scons: *** [Tools/rmsds] Error 1 scons: building terminated because of errors. I can run the compile line successfully when adding "-pthreads", but haven't been able to figure out what file I need to modify in the source code to get scons to successfully compile (couldn't find it after looking in Tools/rmsds.cpp, I'm sure I'm in the wrong place). My guess is this is a simple one-liner that I'm just being a noob about. Thanks for the help, and talk to you soon. Blake |
|
From: LOOS <loo...@gm...> - 2018-08-22 16:51:39
|
Hi Ahmad, If you can’t see the structure in VMD, then that suggests there’s something wrong with the file (or that it’s not an Amber traj file, I suppose). If I were you, I might try re-running the simulation (or a short test) to see if you can reproduce the problem. Alan > On Aug 22, 2018, at 12:19 PM, Ahmad Kiani <ahm...@gm...> wrote: > > Hi Alan, > > Thanks for the reply. DPC.crd is an amber trajectory file. I don't think that it is from the netcdf. I could not see my structure in VMD when I load it. As long as simulation goes everything looks fine in the output log file. > > On Mon, Aug 20, 2018 at 1:49 PM LOOS <loo...@gm... <mailto:loo...@gm...>> wrote: > Hi Ahmad, > > Just to make sure I understand the problem: what format is DPC.crd right now? Is this Amber’s text trajectory file format? That’s the code path where the error is being generated — it looks like that can only happen if you build LOOS without NETCDF support. So, if this is actually a netcdf-format trajectory, you’ll need to build LOOS with netcdf support. You can figure out if you build with netcdf support by looking at config.log in the top-level LOOS distribution direction and searching for netcdf (it should be obvious whether the test for netcdf passed or failed). > > If it’s not a netcdf trajectory, that probably means there’s something fishy in the structure of the file. That error message occurs at the end of trying to read the header. Can you view the trajectory in VMD to verify the format is ok? > > Hope this helps, > > Alan > > >> On Aug 20, 2018, at 1:17 PM, Ahmad Kiani <ahm...@gm... <mailto:ahm...@gm...>> wrote: >> >> Dear all, >> >> I have used chmaber to convert my pdb/psf into crd/prmtop to run them in amber. Now, I want to use traj2dcd to convert the output file (crd file) back to dcd and I am getting the following error. >> >> terminate called after throwing an instance of 'loos::FileOpenError' >> what(): Error while opening DPC.crd >> Problem scanning Amber Trajectory >> Aborted (core dumped) >> >> >> Any help would be appreciated. >> >> Thanks >> Ahmad >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sdm.link/slashdot_______________________________________________ <http://sdm.link/slashdot_______________________________________________> >> Loos-users mailing list >> Loo...@li... <mailto:Loo...@li...> >> https://lists.sourceforge.net/lists/listinfo/loos-users <https://lists.sourceforge.net/lists/listinfo/loos-users> > > ________________________________ > Dr. Alan Grossfield > Associate Professor > Department of Biochemistry and Biophysics > University of Rochester Medical Center > 610 Elmwood Ave, Box 712 > Rochester, NY 14642 > Phone: 585 276 4193 > http://membrane.urmc.rochester.edu <http://membrane.urmc.rochester.edu/> > https://orcid.org/0000-0002-5877-2789 <https://orcid.org/0000-0002-5877-2789> > > ________________________________ Dr. Alan Grossfield Associate Professor Department of Biochemistry and Biophysics University of Rochester Medical Center 610 Elmwood Ave, Box 712 Rochester, NY 14642 Phone: 585 276 4193 http://membrane.urmc.rochester.edu https://orcid.org/0000-0002-5877-2789 |
|
From: LOOS <loo...@gm...> - 2018-08-20 17:49:48
|
Hi Ahmad, Just to make sure I understand the problem: what format is DPC.crd right now? Is this Amber’s text trajectory file format? That’s the code path where the error is being generated — it looks like that can only happen if you build LOOS without NETCDF support. So, if this is actually a netcdf-format trajectory, you’ll need to build LOOS with netcdf support. You can figure out if you build with netcdf support by looking at config.log in the top-level LOOS distribution direction and searching for netcdf (it should be obvious whether the test for netcdf passed or failed). If it’s not a netcdf trajectory, that probably means there’s something fishy in the structure of the file. That error message occurs at the end of trying to read the header. Can you view the trajectory in VMD to verify the format is ok? Hope this helps, Alan > On Aug 20, 2018, at 1:17 PM, Ahmad Kiani <ahm...@gm...> wrote: > > Dear all, > > I have used chmaber to convert my pdb/psf into crd/prmtop to run them in amber. Now, I want to use traj2dcd to convert the output file (crd file) back to dcd and I am getting the following error. > > terminate called after throwing an instance of 'loos::FileOpenError' > what(): Error while opening DPC.crd > Problem scanning Amber Trajectory > Aborted (core dumped) > > > Any help would be appreciated. > > Thanks > Ahmad > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Loos-users mailing list > Loo...@li... > https://lists.sourceforge.net/lists/listinfo/loos-users ________________________________ Dr. Alan Grossfield Associate Professor Department of Biochemistry and Biophysics University of Rochester Medical Center 610 Elmwood Ave, Box 712 Rochester, NY 14642 Phone: 585 276 4193 http://membrane.urmc.rochester.edu https://orcid.org/0000-0002-5877-2789 |
|
From: Ahmad K. <ahm...@gm...> - 2018-08-20 17:17:26
|
Dear all, I have used chmaber to convert my pdb/psf into crd/prmtop to run them in amber. Now, I want to use traj2dcd to convert the output file (crd file) back to dcd and I am getting the following error. terminate called after throwing an instance of 'loos::FileOpenError' what(): Error while opening DPC.crd Problem scanning Amber Trajectory Aborted (core dumped) Any help would be appreciated. Thanks Ahmad |
|
From: LOOS <loo...@gm...> - 2018-07-27 20:55:03
|
Hi Blake, This question has 2 pieces: 1) What should you do? 2) Can you do it with LOOS? For the first part, you can’t do it intelligently with an angle, because of the discontinuity at either 0/360 or -180/180. However, you can do it using a proxy, like cos(theta) or cos^2(theta), which as you point out Dan has done. Or, if the dihedral has its symmetry broken due to interactions with its environment, you might want to use (cos(theta), sin(theta)), but calculating 2D correlations is trickier — you can look up methods for computing circular correlations. Things are simpler if the dihedral effectively fluctuates about a single location (eg a cis double bond), because then you just have make sure you pick a “coordinate system” that avoids the discontinuity. We also have the programs ramachandran and rotamer, for the specific cases of protein backbones and side chains. For the second part, LOOS has a torsion function that takes either 4 atoms or 4 coordinates (see Packages/PyLOOS/domain.py for example usage). It would be very easy to write a simple PyLOOS script that took 4 selections as input and spit out the angle for each frame. Given the angle, you can obviously compute cos(theta), etc. There is a correlation time function in the TimeSeries class (in PyLOOS, it’s TimeSeriesDbl). So, you can store the values in an array, then use that array to create a TimeSeries object, and use the correl() method from that object. Hope this helps, and have a good weekend, Alan > On Jul 27, 2018, at 4:33 PM, Blake Mertz <bla...@ma...> wrote: > > Hello, > > Is it possible to select a dihedral angle in a simulation to calculate a decorrelation time? I know the examples given for this and related tools (bcom and neff) use atom selections, usually for an entire protein (like the GPCRs Tod and Alan studied in their 2011 JCTC paper). > > However, I'm thinking something more along the lines of what Dan Zuckerman has done on the dihedral of butane. If I'm way off-base here, feel free to point this out. Thanks for the help on a Friday! > > Blake > > > -- > Assistant Professor > C. Eugene Bennett Department of Chemistry > (304) 293-9166 > www.mertzlab-biophysics.com <http://www.mertzlab-biophysics.com/index.html> > > "Life is not easy for any of us. But what of that? We must have perseverance and above all confidence in ourselves. We must believe that we are gifted for something and that this thing must be attained." Marie Curie > > "Start by doing what's necessary; then do what's possible; and suddenly you are doing the impossible." St. Francis of Assisi > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Loos-users mailing list > Loo...@li... > https://lists.sourceforge.net/lists/listinfo/loos-users ________________________________ Dr. Alan Grossfield Associate Professor Department of Biochemistry and Biophysics University of Rochester Medical Center 610 Elmwood Ave, Box 712 Rochester, NY 14642 Phone: 585 276 4193 http://membrane.urmc.rochester.edu https://orcid.org/0000-0002-5877-2789 |
|
From: Blake M. <bla...@ma...> - 2018-07-27 20:33:25
|
Hello, Is it possible to select a dihedral angle in a simulation to calculate a decorrelation time? I know the examples given for this and related tools (bcom and neff) use atom selections, usually for an entire protein (like the GPCRs Tod and Alan studied in their 2011 JCTC paper). However, I'm thinking something more along the lines of what Dan Zuckerman has done on the dihedral of butane. If I'm way off-base here, feel free to point this out. Thanks for the help on a Friday! Blake -- Assistant Professor C. Eugene Bennett Department of Chemistry (304) 293-9166 www.mertzlab-biophysics.com <http://www.mertzlab-biophysics.com/index.html> "Life is not easy for any of us. But what of that? We must have perseverance and above all confidence in ourselves. We must believe that we are gifted for something and that this thing must be attained." Marie Curie "Start by doing what's necessary; then do what's possible; and suddenly you are doing the impossible." St. Francis of Assisi |
|
From: Blake M. <me...@gm...> - 2018-05-07 20:03:12
|
Tod,
Thanks for the suggestion -- the updated gmxdump2pdb.pl from git worked as
a standalone. (The version that is bundled with v2.3.2 was still producing
the regex braces error.) I'll get around to directly cloning from git later
this week, now that classes are out and I have a little more free time :--)
Blake
On Mon, Apr 30, 2018 at 5:07 PM, LOOS Maintainer <loo...@gm...>
wrote:
> Hi Eric, Alan is right that you should upgrade to 2.3.2 (or, ideally, use
> the github version). Newer versions of PERL require braces in regular
> expressions to be escaped. That was a bug-fix in 2.3.2. You *could* also
> just download the current gmxdump2pdb.pl from github too, since it
> doesn't have any dependencies on the rest of LOOS. That being said, I'd
> strongly encourage switching to the github version since you'll have the
> latest fixes and additions, and be primed for easily pulling down any
> future changes.
>
> --Tod
>
> PS Sorry for the duplicate email, but I forgot to cc the list...
>
> On Mon, Apr 30, 2018 at 4:02 PM, LOOS <loo...@gm...> wrote:
>
>> Hi Eric,
>>
>> I just ran it through using the most recent LOOS, and didn’t have a
>> problem. If it’s not too painful, my suggestion would be to download the
>> current LOOS from git and rebuild it. I suspect you’re using a newer perl
>> with an older LOOS (before Tod fixed the escaping), and the newer perl now
>> regards the lack of escapes as an error rather than a warning. Just a
>> guess, but it’s worth trying.
>>
>> I hope this helps,
>>
>> Alan
>>
>> PS I’d love to know what you’re running. I pulled the structure up in
>> pymol and it looks really cool. :-)
>>
>> On Apr 30, 2018, at 4:56 PM, Eric Sefah <sef...@gm...> wrote:
>>
>> LOOS version 2.3.1.
>> I used Gromacs version 5.1.2 to generate my tpr file but I'm currently
>> running Gromacs 2016.
>>
>> On 30 April 2018 at 16:29, LOOS <loo...@gm...> wrote:
>>
>>> Your command line looks totally reasonable. That message is presumably
>>> a gromacs complaint, since it’s not a LOOS complaint, and off the top of my
>>> head I don’t know it’s relevant or not.
>>>
>>> Can you send me the tpr? Which version of gromacs was it built with? I
>>> want to see if I can reproduce the error locally.
>>>
>>> For that matter, what version of LOOS are you using? I ask because when
>>> I went through the git log I noticed an entry from 2016 about adding
>>> escapes for braces in regular expression (and also that the line numbers
>>> don’t match the current version). If you’re really using a version from
>>> that long ago, it’s worth upgrading even if we can solve your problem
>>> without it.
>>>
>>> If I’m not able to reproduce your problem, we may need to wait for Tod
>>> to check in, since he wrote gmxdump2pdb.
>>>
>>> Alan
>>>
>>>
>>> On Apr 30, 2018, at 4:21 PM, Eric Sefah <sef...@gm...> wrote:
>>>
>>> Here's my command:
>>>
>>> gmx dump -s run1.tpr | gmxdump2pdb.pl run1_fake
>>>
>>> I just noted a version compatibility issue here.
>>>
>>> "file tpx version 103, software tpx version 112"
>>>
>>> Eric.
>>>
>>>
>>> On 30 April 2018 at 16:16, LOOS <loo...@gm...> wrote:
>>>
>>>> Hi Eric,
>>>>
>>>> Can you send me the command line you’re using? This looks like a bug,
>>>> but for the life of me I can’t imagine why it would happen to you and not
>>>> to us.
>>>>
>>>> Alan
>>>>
>>>> On Apr 30, 2018, at 4:13 PM, Eric Sefah <sef...@gm...> wrote:
>>>>
>>>> Dear LOOS users,
>>>>
>>>> I'm trying to use gmxdump2db.pl to generate pdb and psf from a gromacs
>>>> input file but I get this error:
>>>>
>>>> Unescaped left brace in regex is illegal here in regex; marked by <--
>>>> HERE in m/atom\[(\d+)\]={ <-- HERE name="(.+)"}/ at /usr/local/bin/
>>>> gmxdump2pdb.pl line 375.
>>>>
>>>> I would appreciate some assistance in getting around this problem.
>>>>
>>>> Thank you.
>>>>
>>>> Eric.
>>>> ------------------------------------------------------------
>>>> ------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org <http://slashdot.org/>!
>>>> http://sdm.link/slashdot_______________________________________________
>>>> Loos-users mailing list
>>>> Loo...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/loos-users
>>>>
>>>>
>>>> ___________________________________
>>>> Dr. Alan Grossfield
>>>> Associate Professor
>>>> Department of Biochemistry and Biophysics
>>>> University of Rochester Medical Center
>>>> 610 Elmwood Ave
>>>> <https://maps.google.com/?q=610+Elmwood+Ave&entry=gmail&source=g>, Box
>>>> 712
>>>> Rochester, NY 14642
>>>> Phone: 585 276 4193
>>>> http://membrane.urmc.rochester.edu
>>>>
>>>>
>>>
>>> ___________________________________
>>> Dr. Alan Grossfield
>>> Associate Professor
>>> Department of Biochemistry and Biophysics
>>> University of Rochester Medical Center
>>> 610 Elmwood Ave
>>> <https://maps.google.com/?q=610+Elmwood+Ave&entry=gmail&source=g>, Box
>>> 712
>>> Rochester, NY 14642
>>> Phone: 585 276 4193
>>> http://membrane.urmc.rochester.edu
>>>
>>>
>> <run1.tpr>
>>
>>
>> ___________________________________
>> Dr. Alan Grossfield
>> Associate Professor
>> Department of Biochemistry and Biophysics
>> University of Rochester Medical Center
>> 610 Elmwood Ave, Box 712
>> Rochester, NY 14642
>> Phone: 585 276 4193
>> http://membrane.urmc.rochester.edu
>>
>>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Loos-users mailing list
> Loo...@li...
> https://lists.sourceforge.net/lists/listinfo/loos-users
>
>
|
|
From: LOOS <loo...@gm...> - 2018-05-01 16:29:17
|
Hi Blake, Tod answered — the problem is you’ve got an old version of LOOS, we think. If you clone from github, the problem should go away. I couldn’t reproduce the problem with Eric’s tpr on my machine using the current version. Alan > On May 1, 2018, at 11:59 AM, Blake Mertz <me...@gm...> wrote: > > Alan, > > I encountered that error in trying to use it on some martini-based files from gromacs v5 (and possibly 2016) with loos-2.3.2. I didn't get a chance to go further down the rabbit hole, other than I think that there have been some changes in perl syntax with some recent updates in perl. Perhaps I'm missing something though. Perl version is 5.26.2 on the machine Eric is using. > > Blake > > On Mon, Apr 30, 2018 at 4:29 PM, LOOS <loo...@gm... <mailto:loo...@gm...>> wrote: > Your command line looks totally reasonable. That message is presumably a gromacs complaint, since it’s not a LOOS complaint, and off the top of my head I don’t know it’s relevant or not. > > Can you send me the tpr? Which version of gromacs was it built with? I want to see if I can reproduce the error locally. > > For that matter, what version of LOOS are you using? I ask because when I went through the git log I noticed an entry from 2016 about adding escapes for braces in regular expression (and also that the line numbers don’t match the current version). If you’re really using a version from that long ago, it’s worth upgrading even if we can solve your problem without it. > > If I’m not able to reproduce your problem, we may need to wait for Tod to check in, since he wrote gmxdump2pdb. > > Alan > >> On Apr 30, 2018, at 4:21 PM, Eric Sefah <sef...@gm... <mailto:sef...@gm...>> wrote: >> >> Here's my command: >> >> gmx dump -s run1.tpr | gmxdump2pdb.pl <http://gmxdump2pdb.pl/> run1_fake >> >> I just noted a version compatibility issue here. >> >> "file tpx version 103, software tpx version 112" >> >> Eric. >> >> >> On 30 April 2018 at 16:16, LOOS <loo...@gm... <mailto:loo...@gm...>> wrote: >> Hi Eric, >> >> Can you send me the command line you’re using? This looks like a bug, but for the life of me I can’t imagine why it would happen to you and not to us. >> >> Alan >> >>> On Apr 30, 2018, at 4:13 PM, Eric Sefah <sef...@gm... <mailto:sef...@gm...>> wrote: >>> >>> Dear LOOS users, >>> >>> I'm trying to use gmxdump2db.pl <http://gmxdump2db.pl/> to generate pdb and psf from a gromacs input file but I get this error: >>> >>> Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/atom\[(\d+)\]={ <-- HERE name="(.+)"}/ at /usr/local/bin/gmxdump2pdb.pl <http://gmxdump2pdb.pl/> line 375. >>> >>> I would appreciate some assistance in getting around this problem. >>> >>> Thank you. >>> >>> Eric. >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sdm.link/slashdot_______________________________________________ <http://sdm.link/slashdot_______________________________________________> >>> Loos-users mailing list >>> Loo...@li... <mailto:Loo...@li...> >>> https://lists.sourceforge.net/lists/listinfo/loos-users <https://lists.sourceforge.net/lists/listinfo/loos-users> >> >> ___________________________________ >> Dr. Alan Grossfield >> Associate Professor >> Department of Biochemistry and Biophysics >> University of Rochester Medical Center >> 610 Elmwood Ave <https://maps.google.com/?q=610+Elmwood+Ave&entry=gmail&source=g>, Box 712 >> Rochester, NY 14642 >> Phone: 585 276 4193 >> http://membrane.urmc.rochester.edu <http://membrane.urmc.rochester.edu/> >> > > > ___________________________________ > Dr. Alan Grossfield > Associate Professor > Department of Biochemistry and Biophysics > University of Rochester Medical Center > 610 Elmwood Ave, Box 712 > Rochester, NY 14642 > Phone: 585 276 4193 > http://membrane.urmc.rochester.edu <http://membrane.urmc.rochester.edu/> > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot <http://sdm.link/slashdot> > _______________________________________________ > Loos-users mailing list > Loo...@li... <mailto:Loo...@li...> > https://lists.sourceforge.net/lists/listinfo/loos-users <https://lists.sourceforge.net/lists/listinfo/loos-users> > > ___________________________________ Dr. Alan Grossfield Associate Professor Department of Biochemistry and Biophysics University of Rochester Medical Center 610 Elmwood Ave, Box 712 Rochester, NY 14642 Phone: 585 276 4193 http://membrane.urmc.rochester.edu |
|
From: Blake M. <me...@gm...> - 2018-05-01 15:59:29
|
Alan,
I encountered that error in trying to use it on some martini-based files
from gromacs v5 (and possibly 2016) with loos-2.3.2. I didn't get a chance
to go further down the rabbit hole, other than I think that there have been
some changes in perl syntax with some recent updates in perl. Perhaps I'm
missing something though. Perl version is 5.26.2 on the machine Eric is
using.
Blake
On Mon, Apr 30, 2018 at 4:29 PM, LOOS <loo...@gm...> wrote:
> Your command line looks totally reasonable. That message is presumably a
> gromacs complaint, since it’s not a LOOS complaint, and off the top of my
> head I don’t know it’s relevant or not.
>
> Can you send me the tpr? Which version of gromacs was it built with? I
> want to see if I can reproduce the error locally.
>
> For that matter, what version of LOOS are you using? I ask because when I
> went through the git log I noticed an entry from 2016 about adding escapes
> for braces in regular expression (and also that the line numbers don’t
> match the current version). If you’re really using a version from that
> long ago, it’s worth upgrading even if we can solve your problem without
> it.
>
> If I’m not able to reproduce your problem, we may need to wait for Tod to
> check in, since he wrote gmxdump2pdb.
>
> Alan
>
> On Apr 30, 2018, at 4:21 PM, Eric Sefah <sef...@gm...> wrote:
>
> Here's my command:
>
> gmx dump -s run1.tpr | gmxdump2pdb.pl run1_fake
>
> I just noted a version compatibility issue here.
>
> "file tpx version 103, software tpx version 112"
>
> Eric.
>
>
> On 30 April 2018 at 16:16, LOOS <loo...@gm...> wrote:
>
>> Hi Eric,
>>
>> Can you send me the command line you’re using? This looks like a bug,
>> but for the life of me I can’t imagine why it would happen to you and not
>> to us.
>>
>> Alan
>>
>> On Apr 30, 2018, at 4:13 PM, Eric Sefah <sef...@gm...> wrote:
>>
>> Dear LOOS users,
>>
>> I'm trying to use gmxdump2db.pl to generate pdb and psf from a gromacs
>> input file but I get this error:
>>
>> Unescaped left brace in regex is illegal here in regex; marked by <--
>> HERE in m/atom\[(\d+)\]={ <-- HERE name="(.+)"}/ at /usr/local/bin/
>> gmxdump2pdb.pl line 375.
>>
>> I would appreciate some assistance in getting around this problem.
>>
>> Thank you.
>>
>> Eric.
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org <http://slashdot.org/>!
>> http://sdm.link/slashdot_______________________________________________
>> Loos-users mailing list
>> Loo...@li...
>> https://lists.sourceforge.net/lists/listinfo/loos-users
>>
>>
>> ___________________________________
>> Dr. Alan Grossfield
>> Associate Professor
>> Department of Biochemistry and Biophysics
>> University of Rochester Medical Center
>> 610 Elmwood Ave
>> <https://maps.google.com/?q=610+Elmwood+Ave&entry=gmail&source=g>, Box
>> 712
>> Rochester, NY 14642
>> Phone: 585 276 4193
>> http://membrane.urmc.rochester.edu
>>
>>
>
> ___________________________________
> Dr. Alan Grossfield
> Associate Professor
> Department of Biochemistry and Biophysics
> University of Rochester Medical Center
> 610 Elmwood Ave, Box 712
> Rochester, NY 14642
> Phone: 585 276 4193
> http://membrane.urmc.rochester.edu
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Loos-users mailing list
> Loo...@li...
> https://lists.sourceforge.net/lists/listinfo/loos-users
>
>
|
|
From: Blake M. <bla...@ma...> - 2018-05-01 15:47:21
|
Tod, Thanks for answering my noob question :--) That makes sense. Blake On Tue, May 1, 2018 at 10:50 AM, LOOS Maintainer <loo...@gm...> wrote: > Hi Blake, the short version is that LOOS was originally written to only > support C++98 (i.e. the core C++). Way back when, it was considered a > "good thing" to specify what can throw and what things something can > throw. LOOS has some of those specifications in it. Later on, it was > realized that this approach didn't really live up to it's goal and could > cause more problems than it solved, so it was deprecated (C++11). At some > point, we'll fix that, but in the mean time, you can just ignore those > warnings. > > --Tod > > On Tue, May 1, 2018 at 7:19 AM, Blake Mertz <bla...@ma...> > wrote: > >> Hello, >> >> I'm getting repeated warnings during compile of loos 2.3.2: >> >> dynamic exception specifications are deprecated in C++11 >> >> running Debian v9 (testing repositories), gcc/g++/gfortran v7 and boost >> libraries 1.62. LOOS still compiles, and from what I can tell, the tools >> are functioning properly. I've been unable to find a definitive answer to >> why I'm getting this message from an online search, was hoping to get some >> insights from you guys. Thanks, and talk to you soon. >> >> Blake >> >> -- >> Assistant Professor >> C. Eugene Bennett Department of Chemistry >> (304) 293-9166 >> www.mertzlab-biophysics.com >> <http://www.mertzlab-biophysics.com/index.html> >> >> "Life is not easy for any of us. But what of that? We must have >> perseverance and above all confidence in ourselves. We must believe that we >> are gifted for something and that this thing must be attained." Marie Curie >> >> "Start by doing what's necessary; then do what's possible; and suddenly >> you are doing the impossible." St. Francis of Assisi >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Loos-users mailing list >> Loo...@li... >> https://lists.sourceforge.net/lists/listinfo/loos-users >> >> > -- Assistant Professor C. Eugene Bennett Department of Chemistry (304) 293-9166 www.mertzlab-biophysics.com <http://www.mertzlab-biophysics.com/index.html> "Life is not easy for any of us. But what of that? We must have perseverance and above all confidence in ourselves. We must believe that we are gifted for something and that this thing must be attained." Marie Curie "Start by doing what's necessary; then do what's possible; and suddenly you are doing the impossible." St. Francis of Assisi |
|
From: LOOS M. <loo...@gm...> - 2018-05-01 14:50:32
|
Hi Blake, the short version is that LOOS was originally written to only support C++98 (i.e. the core C++). Way back when, it was considered a "good thing" to specify what can throw and what things something can throw. LOOS has some of those specifications in it. Later on, it was realized that this approach didn't really live up to it's goal and could cause more problems than it solved, so it was deprecated (C++11). At some point, we'll fix that, but in the mean time, you can just ignore those warnings. --Tod On Tue, May 1, 2018 at 7:19 AM, Blake Mertz <bla...@ma...> wrote: > Hello, > > I'm getting repeated warnings during compile of loos 2.3.2: > > dynamic exception specifications are deprecated in C++11 > > running Debian v9 (testing repositories), gcc/g++/gfortran v7 and boost > libraries 1.62. LOOS still compiles, and from what I can tell, the tools > are functioning properly. I've been unable to find a definitive answer to > why I'm getting this message from an online search, was hoping to get some > insights from you guys. Thanks, and talk to you soon. > > Blake > > -- > Assistant Professor > C. Eugene Bennett Department of Chemistry > (304) 293-9166 > www.mertzlab-biophysics.com > <http://www.mertzlab-biophysics.com/index.html> > > "Life is not easy for any of us. But what of that? We must have > perseverance and above all confidence in ourselves. We must believe that we > are gifted for something and that this thing must be attained." Marie Curie > > "Start by doing what's necessary; then do what's possible; and suddenly > you are doing the impossible." St. Francis of Assisi > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Loos-users mailing list > Loo...@li... > https://lists.sourceforge.net/lists/listinfo/loos-users > > |
|
From: Blake M. <bla...@ma...> - 2018-05-01 12:19:15
|
Hello, I'm getting repeated warnings during compile of loos 2.3.2: dynamic exception specifications are deprecated in C++11 running Debian v9 (testing repositories), gcc/g++/gfortran v7 and boost libraries 1.62. LOOS still compiles, and from what I can tell, the tools are functioning properly. I've been unable to find a definitive answer to why I'm getting this message from an online search, was hoping to get some insights from you guys. Thanks, and talk to you soon. Blake -- Assistant Professor C. Eugene Bennett Department of Chemistry (304) 293-9166 www.mertzlab-biophysics.com <http://www.mertzlab-biophysics.com/index.html> "Life is not easy for any of us. But what of that? We must have perseverance and above all confidence in ourselves. We must believe that we are gifted for something and that this thing must be attained." Marie Curie "Start by doing what's necessary; then do what's possible; and suddenly you are doing the impossible." St. Francis of Assisi |
|
From: LOOS M. <loo...@gm...> - 2018-04-30 21:07:10
|
Hi Eric, Alan is right that you should upgrade to 2.3.2 (or, ideally, use
the github version). Newer versions of PERL require braces in regular
expressions to be escaped. That was a bug-fix in 2.3.2. You *could* also
just download the current gmxdump2pdb.pl from github too, since it doesn't
have any dependencies on the rest of LOOS. That being said, I'd strongly
encourage switching to the github version since you'll have the latest
fixes and additions, and be primed for easily pulling down any future
changes.
--Tod
PS Sorry for the duplicate email, but I forgot to cc the list...
On Mon, Apr 30, 2018 at 4:02 PM, LOOS <loo...@gm...> wrote:
> Hi Eric,
>
> I just ran it through using the most recent LOOS, and didn’t have a
> problem. If it’s not too painful, my suggestion would be to download the
> current LOOS from git and rebuild it. I suspect you’re using a newer perl
> with an older LOOS (before Tod fixed the escaping), and the newer perl now
> regards the lack of escapes as an error rather than a warning. Just a
> guess, but it’s worth trying.
>
> I hope this helps,
>
> Alan
>
> PS I’d love to know what you’re running. I pulled the structure up in
> pymol and it looks really cool. :-)
>
> On Apr 30, 2018, at 4:56 PM, Eric Sefah <sef...@gm...> wrote:
>
> LOOS version 2.3.1.
> I used Gromacs version 5.1.2 to generate my tpr file but I'm currently
> running Gromacs 2016.
>
> On 30 April 2018 at 16:29, LOOS <loo...@gm...> wrote:
>
>> Your command line looks totally reasonable. That message is presumably a
>> gromacs complaint, since it’s not a LOOS complaint, and off the top of my
>> head I don’t know it’s relevant or not.
>>
>> Can you send me the tpr? Which version of gromacs was it built with? I
>> want to see if I can reproduce the error locally.
>>
>> For that matter, what version of LOOS are you using? I ask because when
>> I went through the git log I noticed an entry from 2016 about adding
>> escapes for braces in regular expression (and also that the line numbers
>> don’t match the current version). If you’re really using a version from
>> that long ago, it’s worth upgrading even if we can solve your problem
>> without it.
>>
>> If I’m not able to reproduce your problem, we may need to wait for Tod to
>> check in, since he wrote gmxdump2pdb.
>>
>> Alan
>>
>>
>> On Apr 30, 2018, at 4:21 PM, Eric Sefah <sef...@gm...> wrote:
>>
>> Here's my command:
>>
>> gmx dump -s run1.tpr | gmxdump2pdb.pl run1_fake
>>
>> I just noted a version compatibility issue here.
>>
>> "file tpx version 103, software tpx version 112"
>>
>> Eric.
>>
>>
>> On 30 April 2018 at 16:16, LOOS <loo...@gm...> wrote:
>>
>>> Hi Eric,
>>>
>>> Can you send me the command line you’re using? This looks like a bug,
>>> but for the life of me I can’t imagine why it would happen to you and not
>>> to us.
>>>
>>> Alan
>>>
>>> On Apr 30, 2018, at 4:13 PM, Eric Sefah <sef...@gm...> wrote:
>>>
>>> Dear LOOS users,
>>>
>>> I'm trying to use gmxdump2db.pl to generate pdb and psf from a gromacs
>>> input file but I get this error:
>>>
>>> Unescaped left brace in regex is illegal here in regex; marked by <--
>>> HERE in m/atom\[(\d+)\]={ <-- HERE name="(.+)"}/ at /usr/local/bin/
>>> gmxdump2pdb.pl line 375.
>>>
>>> I would appreciate some assistance in getting around this problem.
>>>
>>> Thank you.
>>>
>>> Eric.
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org <http://slashdot.org/>!
>>> http://sdm.link/slashdot_______________________________________________
>>> Loos-users mailing list
>>> Loo...@li...
>>> https://lists.sourceforge.net/lists/listinfo/loos-users
>>>
>>>
>>> ___________________________________
>>> Dr. Alan Grossfield
>>> Associate Professor
>>> Department of Biochemistry and Biophysics
>>> University of Rochester Medical Center
>>> 610 Elmwood Ave
>>> <https://maps.google.com/?q=610+Elmwood+Ave&entry=gmail&source=g>, Box
>>> 712
>>> Rochester, NY 14642
>>> Phone: 585 276 4193
>>> http://membrane.urmc.rochester.edu
>>>
>>>
>>
>> ___________________________________
>> Dr. Alan Grossfield
>> Associate Professor
>> Department of Biochemistry and Biophysics
>> University of Rochester Medical Center
>> 610 Elmwood Ave
>> <https://maps.google.com/?q=610+Elmwood+Ave&entry=gmail&source=g>, Box
>> 712
>> Rochester, NY 14642
>> Phone: 585 276 4193
>> http://membrane.urmc.rochester.edu
>>
>>
> <run1.tpr>
>
>
> ___________________________________
> Dr. Alan Grossfield
> Associate Professor
> Department of Biochemistry and Biophysics
> University of Rochester Medical Center
> 610 Elmwood Ave, Box 712
> Rochester, NY 14642
> Phone: 585 276 4193
> http://membrane.urmc.rochester.edu
>
>
|
|
From: LOOS <loo...@gm...> - 2018-04-30 21:03:03
|
Hi Eric, I just ran it through using the most recent LOOS, and didn’t have a problem. If it’s not too painful, my suggestion would be to download the current LOOS from git and rebuild it. I suspect you’re using a newer perl with an older LOOS (before Tod fixed the escaping), and the newer perl now regards the lack of escapes as an error rather than a warning. Just a guess, but it’s worth trying. I hope this helps, Alan PS I’d love to know what you’re running. I pulled the structure up in pymol and it looks really cool. :-) > On Apr 30, 2018, at 4:56 PM, Eric Sefah <sef...@gm...> wrote: > > LOOS version 2.3.1. > I used Gromacs version 5.1.2 to generate my tpr file but I'm currently running Gromacs 2016. > > On 30 April 2018 at 16:29, LOOS <loo...@gm... <mailto:loo...@gm...>> wrote: > Your command line looks totally reasonable. That message is presumably a gromacs complaint, since it’s not a LOOS complaint, and off the top of my head I don’t know it’s relevant or not. > > Can you send me the tpr? Which version of gromacs was it built with? I want to see if I can reproduce the error locally. > > For that matter, what version of LOOS are you using? I ask because when I went through the git log I noticed an entry from 2016 about adding escapes for braces in regular expression (and also that the line numbers don’t match the current version). If you’re really using a version from that long ago, it’s worth upgrading even if we can solve your problem without it. > > If I’m not able to reproduce your problem, we may need to wait for Tod to check in, since he wrote gmxdump2pdb. > > Alan > > >> On Apr 30, 2018, at 4:21 PM, Eric Sefah <sef...@gm... <mailto:sef...@gm...>> wrote: >> >> Here's my command: >> >> gmx dump -s run1.tpr | gmxdump2pdb.pl <http://gmxdump2pdb.pl/> run1_fake >> >> I just noted a version compatibility issue here. >> >> "file tpx version 103, software tpx version 112" >> >> Eric. >> >> >> On 30 April 2018 at 16:16, LOOS <loo...@gm... <mailto:loo...@gm...>> wrote: >> Hi Eric, >> >> Can you send me the command line you’re using? This looks like a bug, but for the life of me I can’t imagine why it would happen to you and not to us. >> >> Alan >> >>> On Apr 30, 2018, at 4:13 PM, Eric Sefah <sef...@gm... <mailto:sef...@gm...>> wrote: >>> >>> Dear LOOS users, >>> >>> I'm trying to use gmxdump2db.pl <http://gmxdump2db.pl/> to generate pdb and psf from a gromacs input file but I get this error: >>> >>> Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/atom\[(\d+)\]={ <-- HERE name="(.+)"}/ at /usr/local/bin/gmxdump2pdb.pl <http://gmxdump2pdb.pl/> line 375. >>> >>> I would appreciate some assistance in getting around this problem. >>> >>> Thank you. >>> >>> Eric. >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sdm.link/slashdot_______________________________________________ <http://sdm.link/slashdot_______________________________________________> >>> Loos-users mailing list >>> Loo...@li... <mailto:Loo...@li...> >>> https://lists.sourceforge.net/lists/listinfo/loos-users <https://lists.sourceforge.net/lists/listinfo/loos-users> >> >> ___________________________________ >> Dr. Alan Grossfield >> Associate Professor >> Department of Biochemistry and Biophysics >> University of Rochester Medical Center >> 610 Elmwood Ave <https://maps.google.com/?q=610+Elmwood+Ave&entry=gmail&source=g>, Box 712 >> Rochester, NY 14642 >> Phone: 585 276 4193 >> http://membrane.urmc.rochester.edu <http://membrane.urmc.rochester.edu/> >> > > ___________________________________ > Dr. Alan Grossfield > Associate Professor > Department of Biochemistry and Biophysics > University of Rochester Medical Center > 610 Elmwood Ave <https://maps.google.com/?q=610+Elmwood+Ave&entry=gmail&source=g>, Box 712 > Rochester, NY 14642 > Phone: 585 276 4193 > http://membrane.urmc.rochester.edu <http://membrane.urmc.rochester.edu/> > > <run1.tpr> ___________________________________ Dr. Alan Grossfield Associate Professor Department of Biochemistry and Biophysics University of Rochester Medical Center 610 Elmwood Ave, Box 712 Rochester, NY 14642 Phone: 585 276 4193 http://membrane.urmc.rochester.edu |
|
From: LOOS <loo...@gm...> - 2018-04-30 20:29:32
|
Your command line looks totally reasonable. That message is presumably a gromacs complaint, since it’s not a LOOS complaint, and off the top of my head I don’t know it’s relevant or not. Can you send me the tpr? Which version of gromacs was it built with? I want to see if I can reproduce the error locally. For that matter, what version of LOOS are you using? I ask because when I went through the git log I noticed an entry from 2016 about adding escapes for braces in regular expression (and also that the line numbers don’t match the current version). If you’re really using a version from that long ago, it’s worth upgrading even if we can solve your problem without it. If I’m not able to reproduce your problem, we may need to wait for Tod to check in, since he wrote gmxdump2pdb. Alan > On Apr 30, 2018, at 4:21 PM, Eric Sefah <sef...@gm...> wrote: > > Here's my command: > > gmx dump -s run1.tpr | gmxdump2pdb.pl <http://gmxdump2pdb.pl/> run1_fake > > I just noted a version compatibility issue here. > > "file tpx version 103, software tpx version 112" > > Eric. > > > On 30 April 2018 at 16:16, LOOS <loo...@gm... <mailto:loo...@gm...>> wrote: > Hi Eric, > > Can you send me the command line you’re using? This looks like a bug, but for the life of me I can’t imagine why it would happen to you and not to us. > > Alan > >> On Apr 30, 2018, at 4:13 PM, Eric Sefah <sef...@gm... <mailto:sef...@gm...>> wrote: >> >> Dear LOOS users, >> >> I'm trying to use gmxdump2db.pl <http://gmxdump2db.pl/> to generate pdb and psf from a gromacs input file but I get this error: >> >> Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/atom\[(\d+)\]={ <-- HERE name="(.+)"}/ at /usr/local/bin/gmxdump2pdb.pl <http://gmxdump2pdb.pl/> line 375. >> >> I would appreciate some assistance in getting around this problem. >> >> Thank you. >> >> Eric. >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sdm.link/slashdot_______________________________________________ <http://sdm.link/slashdot_______________________________________________> >> Loos-users mailing list >> Loo...@li... <mailto:Loo...@li...> >> https://lists.sourceforge.net/lists/listinfo/loos-users <https://lists.sourceforge.net/lists/listinfo/loos-users> > > ___________________________________ > Dr. Alan Grossfield > Associate Professor > Department of Biochemistry and Biophysics > University of Rochester Medical Center > 610 Elmwood Ave <https://maps.google.com/?q=610+Elmwood+Ave&entry=gmail&source=g>, Box 712 > Rochester, NY 14642 > Phone: 585 276 4193 > http://membrane.urmc.rochester.edu <http://membrane.urmc.rochester.edu/> > ___________________________________ Dr. Alan Grossfield Associate Professor Department of Biochemistry and Biophysics University of Rochester Medical Center 610 Elmwood Ave, Box 712 Rochester, NY 14642 Phone: 585 276 4193 http://membrane.urmc.rochester.edu |
|
From: LOOS <loo...@gm...> - 2018-04-30 20:16:09
|
Hi Eric, Can you send me the command line you’re using? This looks like a bug, but for the life of me I can’t imagine why it would happen to you and not to us. Alan > On Apr 30, 2018, at 4:13 PM, Eric Sefah <sef...@gm...> wrote: > > Dear LOOS users, > > I'm trying to use gmxdump2db.pl <http://gmxdump2db.pl/> to generate pdb and psf from a gromacs input file but I get this error: > > Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/atom\[(\d+)\]={ <-- HERE name="(.+)"}/ at /usr/local/bin/gmxdump2pdb.pl <http://gmxdump2pdb.pl/> line 375. > > I would appreciate some assistance in getting around this problem. > > Thank you. > > Eric. > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Loos-users mailing list > Loo...@li... > https://lists.sourceforge.net/lists/listinfo/loos-users ___________________________________ Dr. Alan Grossfield Associate Professor Department of Biochemistry and Biophysics University of Rochester Medical Center 610 Elmwood Ave, Box 712 Rochester, NY 14642 Phone: 585 276 4193 http://membrane.urmc.rochester.edu |
|
From: Eric S. <sef...@gm...> - 2018-04-30 20:13:47
|
Dear LOOS users,
I'm trying to use gmxdump2db.pl to generate pdb and psf from a gromacs
input file but I get this error:
Unescaped left brace in regex is illegal here in regex; marked by <-- HERE
in m/atom\[(\d+)\]={ <-- HERE name="(.+)"}/ at /usr/local/bin/gmxdump2pdb.pl
line 375.
I would appreciate some assistance in getting around this problem.
Thank you.
Eric.
|
|
From: LOOS <loo...@gm...> - 2018-04-20 01:33:04
|
Hi Chitrak, I hate to say this, but you really need to actually read the manual. atomic-rdf is not the right tool at all — as the name implies, and as the fullhelp states, it computes the rdf atom by atom between all atoms in the first selection and all in the second. The reason it’s slow in your example is you’re basically looking at the rdf between every pair of POPS atoms 1 by 1, which is physically pretty meaningless (and very expensive). Also, since atomic-rdf is a full 3D rdf, it’s not great for looking at lateral organization anyway, because the peaks are absurdly high close in but then decay to way below 1. If you’re looking for bridging sodiums, you could do 2 things with existing code. One, you could run xy_rdf and look to see if presence of salt changes the packing of the lipids (I’d use either the phosphates or the whole headgroup for the selection). Two, you could use atomic-rdf and pick the sodiums and the phosphate oxygens as the two selections, to see if the sodium is enriched around the phosphate oxygens. However, neither of these will find bridging sodiums directly. For that, you’d need to write a pyloos script. We did something like this way back for our beta2 adrenergic receptor paper, but the script would be easy to write. Basically, you select all of the phosphate oxygens, then split by residue so that each lipid's oxygens are in its own AtomicGroup, and do the same for the sodiums. You then do a double loop over atomic groups: for sod in sodium_groups: num_lipids_in_contact = 0 for phosphate in phosphate_groups: if sod.contactWith(phosphate, box): # box is the periodicBox() num_lipids_in_contact += 1 if num_lipids_in_contact > 1: print “found sodium bridging lipids" Note: this code is just a sketch — I didn’t run it, let alone check it. Hope this helps, Alan > On Apr 19, 2018, at 8:38 PM, Chitrak Gupta <ch...@mi...> wrote: > > Hi, > > I am trying to look at clustering of lipids in my trajectories. Some systems contain two different lipids (POPC and POPS) and I want to see if the lipids are arranging themselves in a pattern. Another simulation has POPC as a function of ionic strength, and I want to see if the Na+ ions are bridging headgroup oxygens from multiple lipids. > > For one, is RDF the best tool for this? I am trying to do POPC-POPC rdf and also POPC-POPS and POPS-POPS rdf. > > Second, the script seems to be running really slow. I have 100 lipids per leaflet, system size is ~ 83000 atoms and number of frames range from anywhere between 4000 and 9000. > > Here is what I am doing > > atomic-rdf model.pdb trajectory.dcd --skip 20 'segname == "POPS"' 'segname == "POPS"' 0 20 40 > > > Is there a better tool and/or a more efficient way to run the atomic-rdf tool? > > > Best, > Chitrak. > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Loos-users mailing list > Loo...@li... > https://lists.sourceforge.net/lists/listinfo/loos-users ___________________________________ Dr. Alan Grossfield Associate Professor Department of Biochemistry and Biophysics University of Rochester Medical Center 610 Elmwood Ave, Box 712 Rochester, NY 14642 Phone: 585 276 4193 http://membrane.urmc.rochester.edu |