<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" >

<channel><title><![CDATA[Molecular Modeling and Drug Design - Blog]]></title><link><![CDATA[http://www.drugdesign.gr/blog]]></link><description><![CDATA[Blog]]></description><pubDate>Sat, 11 Apr 2026 01:35:08 -0700</pubDate><generator>Weebly</generator><item><title><![CDATA[Maestro ​Error: x server has no opengl glx extension]]></title><link><![CDATA[http://www.drugdesign.gr/blog/maestro-error-x-server-has-no-opengl-glx-extension-maestro]]></link><comments><![CDATA[http://www.drugdesign.gr/blog/maestro-error-x-server-has-no-opengl-glx-extension-maestro#comments]]></comments><pubDate>Mon, 10 Feb 2025 21:31:40 GMT</pubDate><category><![CDATA[Uncategorized]]></category><guid isPermaLink="false">http://www.drugdesign.gr/blog/maestro-error-x-server-has-no-opengl-glx-extension-maestro</guid><description><![CDATA[**************************************************************Maestro Molecular Modeling InterfaceMaestro is a product of Schr&ouml;dinger, Inc.Legal notices can be viewed by clicking Help-&gt;About Maestro**************************************************************/bin/sh: 1: glxinfo: not foundlibGL error: MESA-LOADER: failed to open nouveau: /opt/schrodinger2024-2/maestro-v14.0/lib/Linux-x86_64/gl/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /opt/sc [...] ]]></description><content:encoded><![CDATA[<div class="paragraph"><br />**************************************************************<br />Maestro Molecular Modeling Interface<br />Maestro is a product of Schr&ouml;dinger, Inc.<br />Legal notices can be viewed by clicking Help-&gt;About Maestro<br />**************************************************************<br />/bin/sh: 1: glxinfo: not found<br />libGL error: MESA-LOADER: failed to open nouveau: /opt/schrodinger2024-2/maestro-v14.0/lib/Linux-x86_64/gl/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /opt/schrodinger2024-2/maestro-v14.0/lib/Linux-x86_64/gl, suffix _dri)<br />libGL error: failed to load driver: nouveau<br /><br />&#8203;Error:&nbsp;<span>x server has no opengl glx extension maestro</span><br />Fix:&nbsp;<span>After I executed this command, it worked fine:</span><br />export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6<br />&nbsp;<br />But we need to open Maestro in the shell, for example:<br />cd &lt;your path&gt;/schrodinger20xx-x<br />export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6<br />./maestro<br />&nbsp;<br />Or directly modify the Maestro startup script<br />vim ./maestro<br />Add to the first line<br />export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6<br />I tried the following and it worked<br /><br /><span>I referred to the following links</span><br /><span><a href="https://www.researchgate.net/deref/https%3A%2F%2Fgithub.com%2Fconda-forge%2Fctng-compilers-feedstock%2Fissues%2F95?_tp=eyJjb250ZXh0Ijp7ImZpcnN0UGFnZSI6InF1ZXN0aW9uIiwicGFnZSI6InF1ZXN0aW9uIn19" target="_blank">https://github.com/conda-forge/ctng-compilers-feedstock/issues/95</a></span><br /><br /><strong>What worked for me is to add the following in the<span>&nbsp;.bashrc script:</span></strong><strong>export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6</strong><br /><strong>source&nbsp;<span>.bashrc&nbsp;</span></strong><br />&nbsp;<br />Schrodinger response:<br><span>The error usually indicates that you have not installed drivers with hardware accelerated&nbsp;<span>OpenGL</span>. Try launching&nbsp;<span>Maestro</span>&nbsp;with the -SGL option</span><span>$SCHRODINGER/<span>maestro</span>&nbsp;-SGL</span>&#8203;<br /><br /><span></span><span>Please refer to the following KB articles for more information:</span><br /><span></span><span><a href="https://support.schrodinger.com/kA08V000000LUPC?name=370" target="_blank">I just installed the latest version of Schr&ouml;dinger software on a new computer and I am receiving some&nbsp;<span>OpenGL</span>&nbsp;<span>GLX</span>&nbsp;errors. What do they</a></span><br /><span></span><br /><span><a href="https://support.schrodinger.com/kA08V000000LULg?name=1281" target="_blank">Can I run&nbsp;<span>Maestro</span>&nbsp;on a remote machine and display to my local machine?</a></span><br /><span>&nbsp;</span><br />Zoe<br /><br /></div>]]></content:encoded></item><item><title><![CDATA[Using hydrogen bond constraints vs all-atom bond constraints in GROMACS]]></title><link><![CDATA[http://www.drugdesign.gr/blog/october-09th-2024]]></link><comments><![CDATA[http://www.drugdesign.gr/blog/october-09th-2024#comments]]></comments><pubDate>Wed, 09 Oct 2024 07:44:32 GMT</pubDate><category><![CDATA[Uncategorized]]></category><guid isPermaLink="false">http://www.drugdesign.gr/blog/october-09th-2024</guid><description><![CDATA[Whether one will&nbsp;use hydrogen bond constraints vs all-atom bond constraints in GROMACS depends on the force field to be used.The CHARMM36m force field&nbsp;is the only one in Gromacs, where constraining only hydrogen bonds is mandatory (as noted in the Gromacs manual:&nbsp;https://manual.gromacs.org/current/user-guide/force-fields.html).In other force fields, both hydrogen bond constraints and full bond constraints are possible, but full bond constraints are typically chosen when the goal i [...] ]]></description><content:encoded><![CDATA[<div class="paragraph"><font size="3">Whether one will&nbsp;use hydrogen bond constraints vs all-atom bond constraints in GROMACS depends on the force field to be used.<br /><br />The CHARMM36m force field&nbsp;is the only one in Gromacs, where constraining only hydrogen bonds is mandatory (as noted in the Gromacs manual:&nbsp;<a href="https://manual.gromacs.org/current/user-guide/force-fields.html" target="_blank"><span>https</span><span>://manual</span><span>.gromacs</span><span>.org</span><span>/current</span><span>/user</span><span>-guide</span><span>/force</span><span>-fields</span><span>.html</span></a>).<br /><br />In other force fields, both hydrogen bond constraints and full bond constraints are possible, but full bond constraints are typically chosen when the goal is to simulate longer timescales within shorter simulation durations.<br /><br />If your focus is on accuracy rather than rapidly reaching long timescales, it is best to use&nbsp;the hydrogen bond option. This approach is also applied in DNA simulations, where the hydrogen bond option was used (<a href="https://gromacs.bioexcel.eu/t/mdp-parameters-for-non-bonded-interaction-using-the-amber-force-field/6458" target="_blank"><span>https</span><span>://gromacs</span><span>.bioexcel</span><span>.eu</span><span>/t</span><span>/mdp</span><span>-parameters</span><span>-for</span><span>-non</span><span>-bonded</span><span>-interaction</span><span>-using</span><span>-the</span><span>-amber</span><span>-force</span><span>-field</span><span>/6458</span></a>).&nbsp;<br /><br />In general the option&nbsp;<span style="color:rgb(44, 54, 58)">constraints=h-bonds is more compatible with other software, eg. NAMD, where particular&nbsp;&nbsp;</span>constraints in&nbsp;hbond fixes https://pubs.acs.org/doi/10.1021/acs.jctc.2c00200 are used.<br /><br />Ultimatitely, the choice of whether to use constraints=h-bonds&nbsp;or constraints=all-bonds&nbsp;constraints depends on how the force field is parameterized.&nbsp;<br /><br />From&nbsp;<a href="https://manual.gromacs.org/2019.2/release-notes/2019/major/miscellaneous.html" target="_blank">here</a>&nbsp;we can understand that&nbsp;<em>common forcefields, including AMBER, CHARMM and OPLS/aa, are parametrized with hydrogen constrained bonds. Constraining all bonds should be avoided for correctness.&nbsp;</em></font><br /><br /><br /><font size="3">Michalis and Matilde</font><br /><br /></div>]]></content:encoded></item><item><title><![CDATA[How to create an image from PowerPoint without losing quality]]></title><link><![CDATA[http://www.drugdesign.gr/blog/how-to-create-an-image-from-powerpoint-without-losing-quality]]></link><comments><![CDATA[http://www.drugdesign.gr/blog/how-to-create-an-image-from-powerpoint-without-losing-quality#comments]]></comments><pubDate>Mon, 08 Apr 2024 09:34:33 GMT</pubDate><category><![CDATA[Uncategorized]]></category><guid isPermaLink="false">http://www.drugdesign.gr/blog/how-to-create-an-image-from-powerpoint-without-losing-quality</guid><description><![CDATA[Before starting to add elements to your PowerPoint file, the options of the file in question must be appropriately set to save all pasted images in their original resolution and high fidelity. If you have a PowerPoint file with images in it already, change the file options and then import/paste the original images again into the document to preserve their original resolution, as the images that were imported before setting these quality options have already been compressed.&nbsp;To change the fi [...] ]]></description><content:encoded><![CDATA[<div class="paragraph"><font size="3">Before starting to add elements to your PowerPoint file, the options of the file in question must be appropriately set to save all pasted images in their original resolution and high fidelity. If you have a PowerPoint file with images in it already, change the file options and then import/paste the original images again into the document to preserve their original resolution, as the images that were imported before setting these quality options have already been compressed.<br />&nbsp;<br />To change the file options for original image resolution and high fidelity, go to &ldquo;Options&rdquo; and make sure the following options are selected in the &ldquo;Image Size and Quality&rdquo; of the &ldquo;Advanced&rdquo; tab:</font></div>  <div><div class="wsite-image wsite-image-border-none " style="padding-top:10px;padding-bottom:10px;margin-left:0;margin-right:0;text-align:center"> <a> <img src="http://www.drugdesign.gr/uploads/7/6/0/2/7602318/slide1_orig.jpg" alt="Picture" style="width:auto;max-width:100%" /> </a> <div style="display:block;font-size:90%"></div> </div></div>  <div class="paragraph"><font size="3">Finally, remember to double-check that you are saving/exporting your PowerPoint file to other formats maintaining the image quality. When &ldquo;Saving as&rdquo;, select &ldquo;Tools&rdquo; &rarr; &ldquo;Compress pictures&rdquo;&nbsp;options and ensure that &ldquo;High fidelity&rdquo; is selected before saving.</font></div>  <div><div class="wsite-image wsite-image-border-none " style="padding-top:10px;padding-bottom:10px;margin-left:0;margin-right:0;text-align:center"> <a> <img src="http://www.drugdesign.gr/uploads/7/6/0/2/7602318/slide2_orig.jpg" alt="Picture" style="width:auto;max-width:100%" /> </a> <div style="display:block;font-size:90%"></div> </div></div>  <div class="paragraph"><font size="3">P.S.: to interconvert between image formats without losing quality, my first choice is <a href="https://www.zamzar.com/">https://www.zamzar.com/</a>, although it has some size/amount of conversions limitations in its free version.<br /><br /><br />&#8203;Francho Ner&iacute;n Fonz</font></div>]]></content:encoded></item><item><title><![CDATA[PLUMED Grid Issue]]></title><link><![CDATA[http://www.drugdesign.gr/blog/plumed-grid-issue]]></link><comments><![CDATA[http://www.drugdesign.gr/blog/plumed-grid-issue#comments]]></comments><pubDate>Tue, 04 Oct 2022 15:03:09 GMT</pubDate><category><![CDATA[Uncategorized]]></category><guid isPermaLink="false">http://www.drugdesign.gr/blog/plumed-grid-issue</guid><description><![CDATA[- ProblemI recently noted one of the systems we are simulating suffered from decreasing performance as the simulation progressed. Further investigation revealed it is&nbsp;not the actual performance of the simulation that was lower, but the fact that&nbsp;PLUMED needed increasingly large amounts of time to pre-process the HILLS file&nbsp;for each replica.This is not an issue for a short-running simulation but for one where the&nbsp;simulation time runs into several &mu;s (such as Coarse-grained  [...] ]]></description><content:encoded><![CDATA[<div class="paragraph"><strong>- Problem</strong><br /><br />I recently noted one of the systems we are simulating suffered from decreasing performance as the simulation progressed. Further investigation revealed it is&nbsp;not the actual performance of the simulation that was lower, but the fact that&nbsp;PLUMED needed increasingly large amounts of time to pre-process the HILLS file&nbsp;for each replica.<br /><br />This is not an issue for a short-running simulation but for one where the&nbsp;simulation time runs into several &mu;s (such as Coarse-grained simulations), it&nbsp;can completely hinder the trajectory from progressing past a certain point in&nbsp;time.<br /><br /><strong>- Solution</strong><br /><br />Comparisons with other systems and similar issues mentioned in the issues of&nbsp;the PLUMED github repository, as well as in the PLUMED mailing list, pointed&nbsp;in the direction of a grid-related setting being the cause of the delay, specifically, the fineness/coarseness of the grid.&nbsp;<br /><br />The two files below (CORRECT PLUMED INPUT FILE &amp; OLD <span>PLUMED INPUT FILE</span>)&nbsp;highlight a different way of specifying the grid density.<br /><br />In the `old` file, the grid spacing was manually specified with the&nbsp;GRID_SPACING argument in the METAD block.<br /><br />In the `correct` file, that line is absent from the file. In the absence of a&nbsp;GRID_SPACING or a GRID_BIN argument, PLUMED is going to use a grid spacing&nbsp;value equal to 1/5 of the Collective Variable (CV) width, for each CV,&nbsp;espectively.<br /><br />Further testing is required but this value appears to be a robust default and&nbsp;has solved this issue in this particular instance.<br /><br /><br /><strong><font color="#c23b3b">CORRECT PLUMED INPUT FILE</font></strong><br /><br /><span>C1: RMSD REFERENCE=rmsd_reference.pdb TYPE=OPTIMAL</span><br /><br /><span>COM1: CENTER ATOMS=1-122</span><br /><span>COM2: CENTER ATOMS=123-244</span><br /><br /><span>D1: DISTANCE ATOMS=COM1,COM2</span><br /><br /><span>METAD ...</span><br /><span>ARG=C1,D1</span><br /><span>SIGMA=0.4,0.8</span><br /><span>HEIGHT=0.005</span><br /><span>PACE=100</span><br /><span>LABEL=meta</span><br /><span>BIASFACTOR=2.0</span><br /><span>TEMP=300</span><br /><span>GRID_MIN=0,1</span><br /><span>GRID_MAX=4.5,6</span><br /><span>... METAD</span><br /><span>UPPER_WALLS ARG=C1 AT=4 KAPPA=300.0 EXP=2 EPS=1 OFFSET=0 LABEL=uwall</span><br /><span>UPPER_WALLS ARG=D1 AT=5.5 KAPPA=300.0 EXP=2 EPS=1 OFFSET=0 LABEL=u2wall</span><br /><br /><span># monitor the two variables and the metadynamics bias potential</span><br /><span>PRINT STRIDE=10000 ARG=C1,D1,meta.bias FILE=COLVAR</span><br />&#8203;<br /><br /><br /><strong><font color="#c23b3b">OLD INPUT PLUMED FILE (do not use!)</font></strong><br /><br /><span>C1: RMSD REFERENCE=rmsd_reference.pdb TYPE=OPTIMAL</span><br /><br /><span>COM1: CENTER ATOMS=1-122</span><br /><span>COM2: CENTER ATOMS=123-244</span><br /><br /><span>D1: DISTANCE ATOMS=COM1,COM2</span><br /><br /><span>METAD ...</span><br /><span>ARG=C1,D1</span><br /><span>SIGMA=0.4,0.8</span><br /><span>HEIGHT=0.005</span><br /><span>PACE=100</span><br /><span>LABEL=meta</span><br /><span>BIASFACTOR=2.0</span><br /><span>TEMP=300</span><br /><span>GRID_MIN=0,1</span><br /><span>GRID_MAX=4.5,6</span><br /><span>GRID_SPACING=0.01,0.01</span><br /><span>... METAD</span><br /><span>UPPER_WALLS ARG=C1 AT=4 KAPPA=300.0 EXP=2 EPS=1 OFFSET=0 LABEL=uwall</span><br /><span>UPPER_WALLS ARG=D1 AT=5.5 KAPPA=300.0 EXP=2 EPS=1 OFFSET=0 LABEL=u2wall</span><br /><br /><span># monitor the two variables and the metadynamics bias potential</span><br /><span>PRINT STRIDE=10000 ARG=C1,D1,meta.bias FILE=COLVAR</span><br /><br /></div>]]></content:encoded></item><item><title><![CDATA[File Transfer issue & solution]]></title><link><![CDATA[http://www.drugdesign.gr/blog/file-transfer-issue-solution]]></link><comments><![CDATA[http://www.drugdesign.gr/blog/file-transfer-issue-solution#comments]]></comments><pubDate>Tue, 04 Oct 2022 14:58:45 GMT</pubDate><category><![CDATA[Uncategorized]]></category><guid isPermaLink="false">http://www.drugdesign.gr/blog/file-transfer-issue-solution</guid><description><![CDATA[- ProblemFiles/folders might become corrupted when transferring between computers oreven disks, in a way that is non obvious to your code so it won't throw awarning, but might still affect the validity of your data.- SolutionThis problem can occur when transferring files between one cluster and anotherbut it can also occur at any point when file transfer is taking place, i.e.&nbsp;* Transfer file from internal to external disk drive&nbsp;* Transfer file from one internal disk drive to another in [...] ]]></description><content:encoded><![CDATA[<div class="paragraph">- Problem<br /><br />Files/folders might become corrupted when transferring between computers or<br />even disks, in a way that is non obvious to your code so it won't throw a<br />warning, but might still affect the validity of your data.<br /><br />- Solution<br /><br />This problem can occur when transferring files between one cluster and another<br />but it can also occur at any point when file transfer is taking place, i.e.<br /><br />&nbsp;* Transfer file from internal to external disk drive<br />&nbsp;* Transfer file from one internal disk drive to another internal disk drive<br />&nbsp;* Transfer file from one computer to another over the network<br /><br />It can even take place when no operations are being performed on the file at<br />all. This is called bit rot and data centers that specialise in archival and<br />where data integrity is of high importance, employ specialised hardware and<br />software to detect and correct it.<br /><br />For our purposes, what we can do is focus on best practices when downloading<br />or uploading files from or to a location. This boils down to two things:<br /><br />(1) Instead of transferring multiple small files and folders it is better to<br />&nbsp; &nbsp; transfer a single item instead.<br /><br />&nbsp; &nbsp; This can be achieved with a command like<br /><br />&nbsp; &nbsp; `tar -czf directory.tgz directory` if we are interested in transferring<br />&nbsp; &nbsp; a single directory but can, of course, accomodate as many folders as we<br />&nbsp; &nbsp; require.<br /><br />&nbsp; &nbsp; For the next step we need a way of generating a unique "identity" for the<br />&nbsp; &nbsp; tgz archive. For this we can use a checksum. One way of computing one can<br />&nbsp; &nbsp; be seen in the command below:<br /><br />&nbsp; &nbsp; `md5sum directory.tgz`<br /><br />&nbsp; &nbsp; This will print a string of alphanumeric characters (the aforementioned<br />&nbsp; &nbsp; "identity" of the file) followed by white-space and the filename. The<br />&nbsp; &nbsp; output of the command can be stored in a file for easier comparison. After<br />&nbsp; &nbsp; transferring the file to the destination we can run the `md5sum` command<br />&nbsp; &nbsp; there as well and verify the hashes are identical.<br /><br />&nbsp; &nbsp; An added benefit of transferring data in a single archive is that it is<br />&nbsp; &nbsp; faster, as our file transfer program of choice (e.g. `scp`, or `rsync`)<br />&nbsp; &nbsp; only needs to negotiate a single connection.<br /><br />(2) Alternatively, assuming it doesn't make sense to bundle our data in a<br />&nbsp; &nbsp; single archive, we can run `md5sum` on all files to be transferred and<br />&nbsp; &nbsp; compare all of the checksums before and after the transfer. This can be<br />&nbsp; &nbsp; achieved in many ways but one command that would do the trick is:<br /><br />&nbsp; &nbsp; `find -L . -type f | xargs md5sum | sort -Vk2`<br /><br />&nbsp; &nbsp; This can be run from a location that contains all of the files you want to<br />&nbsp; &nbsp; transfer. An short explanation about the various flags follows:<br /><br />&nbsp; &nbsp; `-L`: This instructs `find` to follow symlinks<br />&nbsp; &nbsp; `.`: This instructs `find` to search in the current directory<br />&nbsp; &nbsp; `-type f`: This instructs `find` to only identify files<br /><br />&nbsp; &nbsp; `xargs md5sum`: Run `md5sum` on all detected files<br /><br />&nbsp; &nbsp; `sort -Vk2`: Sort the results lexicographically by file name to avoid<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;differences in the default sorting order due to location<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;settings<br /><br />&nbsp; &nbsp; The two files produced by the above command (before and after transfer),<br />&nbsp; &nbsp; can be compared to ensure the transferred files are identical.<br /><br />&#8203;Panos<br /></div>]]></content:encoded></item><item><title><![CDATA[Updating Ubuntu packages]]></title><link><![CDATA[http://www.drugdesign.gr/blog/updating-ubuntu-packages]]></link><comments><![CDATA[http://www.drugdesign.gr/blog/updating-ubuntu-packages#comments]]></comments><pubDate>Wed, 15 Dec 2021 10:04:57 GMT</pubDate><category><![CDATA[Uncategorized]]></category><guid isPermaLink="false">http://www.drugdesign.gr/blog/updating-ubuntu-packages</guid><description><![CDATA[sudo apt-get updatesudo apt-get cleansudo apt-get updatesudo apt-get upgradesudo apt-get dist-upgradeYou can also try:sudo&nbsp; apt full-upgrade [...] ]]></description><content:encoded><![CDATA[<div class="paragraph"><font size="3">sudo apt-get update<br /><br />sudo apt-get clean<br /><br />sudo apt-get update<br /><br />sudo apt-get upgrade<br /><br /><span>sudo apt-get dist-upgrade<br /><br />You can also try:</span><br />sudo&nbsp; apt full-upgrade</font></div>]]></content:encoded></item><item><title><![CDATA[Ubuntu 20.04 start screen frozen at system check  (Ctrl-C to stop system checks does not work)]]></title><link><![CDATA[http://www.drugdesign.gr/blog/ubuntu-2004-start-screen-frozen-at-system-check-ctrl-c-to-stop-system-checks-does-not-work]]></link><comments><![CDATA[http://www.drugdesign.gr/blog/ubuntu-2004-start-screen-frozen-at-system-check-ctrl-c-to-stop-system-checks-does-not-work#comments]]></comments><pubDate>Wed, 15 Dec 2021 09:37:10 GMT</pubDate><category><![CDATA[Uncategorized]]></category><guid isPermaLink="false">http://www.drugdesign.gr/blog/ubuntu-2004-start-screen-frozen-at-system-check-ctrl-c-to-stop-system-checks-does-not-work</guid><description><![CDATA[1) Install the recommended NVIDIA drivers for your graphics card:sudo add-apt-repository ppa:graphics-drivers/ppaubuntu-drivers devicessudo apt install [driver_name]orsudo ubuntu-drivers autoinstallsudo reboot2) you may have to uninstall all nvidia drivers firstdpkg -l | grep -i nvidiasudo apt-get remove --purge '^nvidia-.*'sudo apt-get install ubuntu-desktopsudo reboot3) Disable&nbsp;nvidia-drm modeset optionI discovered that prime-select writes a configuration file which causes the problem. It [...] ]]></description><content:encoded><![CDATA[<div class="paragraph"><font size="3"><strong>1) Install the recommended NVIDIA drivers for your graphics card:</strong><br /><br /><span style="color:rgb(64, 64, 64)">sudo add-apt-repository ppa:graphics-drivers/ppa<br /><br />ubuntu-drivers devices<br /><br />sudo apt install [driver_name]<br />or<br />sudo ubuntu-drivers autoinstall<br /><br />sudo reboot<br /><br /><strong>2) you may have to uninstall all nvidia drivers first</strong><br /><br />dpkg -l | grep -i nvidia<br /><br />sudo apt-get remove --purge '^nvidia-.*'<br /><br />sudo apt-get install ubuntu-desktop<br /><br />sudo reboot<br /><br /><strong>3) Disable&nbsp;</strong></span><strong><span style="color:rgb(35, 38, 41)">nvidia-drm modeset option</span></strong><br /><br />I discovered that prime-select writes a configuration file which causes the problem. It enables the nvidia-drm modeset option. You can simply undo the change made by prime-select by commenting out this option. It will not be reset, because prime-select only writes this file when it does not exist yet."<br />Open the file in your favorite editor (vim, nano, gedit, etc.).<br />sudo nano /lib/modprobe.d/nvidia-kms.conf And comment out the the nvidia-drm modeset option.<br /># This file was generated by nvidia-prime # Set value to 0 to disable modesetting # options nvidia-drm modeset=1</font></div>]]></content:encoded></item><item><title><![CDATA[LiPyphilic: A Python Toolkit for the Analysis of Lipid Membrane Simulations]]></title><link><![CDATA[http://www.drugdesign.gr/blog/lipyphilic-a-python-toolkit-for-the-analysis-of-lipid-membrane-simulations]]></link><comments><![CDATA[http://www.drugdesign.gr/blog/lipyphilic-a-python-toolkit-for-the-analysis-of-lipid-membrane-simulations#comments]]></comments><pubDate>Mon, 30 Aug 2021 16:13:03 GMT</pubDate><category><![CDATA[Uncategorized]]></category><guid isPermaLink="false">http://www.drugdesign.gr/blog/lipyphilic-a-python-toolkit-for-the-analysis-of-lipid-membrane-simulations</guid><description><![CDATA[LiPyphilic is a Python package for analyzing such simulations. Analysis tools in LiPyphilic include the identification of cholesterol flip-flop events, the classification of local lipid environments, and the degree of interleaflet registration. LiPyphilic is both force field- and resolution-agnostic, and by using the powerful atom selection language of MDAnalysis, it can handle membranes with highly complex compositions. LiPyphilic also offers two on-the-fly trajectory transformations to (i) fix [...] ]]></description><content:encoded><![CDATA[<div class="paragraph"><font size="3"><span style="color:rgb(0, 0, 0)">LiPyphilic is a Python package for analyzing such simulations. Analysis tools in LiPyphilic include the identification of cholesterol flip-flop events, the classification of local lipid environments, and the degree of interleaflet registration. LiPyphilic is both force field- and resolution-agnostic, and by using the powerful atom selection language of MDAnalysis, it can handle membranes with highly complex compositions. LiPyphilic also offers two on-the-fly trajectory transformations to (i) fix membranes split across periodic boundaries and (ii) perform nojump coordinate unwrapping. Implementation of nojump unwrapping accounts for fluctuations in the box volume under the&nbsp;</span><em style="color:rgb(0, 0, 0)">NPT</em><span style="color:rgb(0, 0, 0)">&nbsp;ensemble&mdash;an issue that most current implementations have overlooked. The full documentation of LiPyphilic, including installation instructions and links to interactive online tutorials, is available at&nbsp;</span><a href="https://lipyphilic.readthedocs.io/en/latest">https://lipyphilic.readthedocs.io/en/latest</a><span style="color:rgb(0, 0, 0)">.<br /><br />Publication can be found here:&nbsp;</span></font><span><font size="4"><a href="https://pubs.acs.org/doi/10.1021/acs.jctc.1c00447" target="_blank">https://pubs.acs.org/doi/10.1021/acs.jctc.1c00447</a></font></span><span>&#8203;</span></div>]]></content:encoded></item><item><title><![CDATA[Mounting a new disk on Ubuntu - permissions]]></title><link><![CDATA[http://www.drugdesign.gr/blog/mounting-a-new-disk-on-ubuntu-permissions]]></link><comments><![CDATA[http://www.drugdesign.gr/blog/mounting-a-new-disk-on-ubuntu-permissions#comments]]></comments><pubDate>Thu, 22 Jul 2021 13:50:05 GMT</pubDate><category><![CDATA[Uncategorized]]></category><guid isPermaLink="false">http://www.drugdesign.gr/blog/mounting-a-new-disk-on-ubuntu-permissions</guid><description><![CDATA[When mounting a new disk on Ubuntu the default permissions are:rw,nosuid,nodev,noexec,relatimewhich don't allow one to execute programs.The solution is to remove the 'noexec' option with&#8203;noexec &mu;&epsilon; mount -o remount,rw,nosuid,nodev,relatime /media/mydata3Alexis [...] ]]></description><content:encoded><![CDATA[<h2 class="wsite-content-title"><font size="3"><span style="color: rgb(51, 51, 51); font-weight: 400;">When mounting a new disk on Ubuntu the default permissions are:<br />rw,nosuid,nodev,noexec,relatime</span><br /><span style="color: rgb(51, 51, 51); font-weight: 400;"><br />which don't allow one to execute programs.<br /><br />The solution is to remove the 'noexec' option with<br />&#8203;<br />noexec &mu;&epsilon; mount -o remount,rw,nosuid,nodev,relatime /media/mydata3</span><br /></font><span style="color:rgb(51, 51, 51); font-weight:400"><font size="3"><br />Alexis<br /></font></span><br /></h2>]]></content:encoded></item><item><title><![CDATA[Upgrading to the next Ubuntu  LTS]]></title><link><![CDATA[http://www.drugdesign.gr/blog/upgrading-to-the-next-ubuntu-lts]]></link><comments><![CDATA[http://www.drugdesign.gr/blog/upgrading-to-the-next-ubuntu-lts#comments]]></comments><pubDate>Mon, 19 Jul 2021 17:12:48 GMT</pubDate><category><![CDATA[Uncategorized]]></category><guid isPermaLink="false">http://www.drugdesign.gr/blog/upgrading-to-the-next-ubuntu-lts</guid><description><![CDATA[You can&nbsp;jump between Ubuntu&nbsp; LTS versions but if you are not on the LTS you 'd have to first update to the next Ubuntu version.Be sure to fully update your current OS:sudo apt-get updatesudo apt-get upgradeThen try 'sudo apt install update-manager-core' to check for any broken dependenciesFix any broken problems, usually by removing them and re-installing them.sudo shutdown -r nowThen, sudo&nbsp; do-release-upgrade [...] ]]></description><content:encoded><![CDATA[<div class="paragraph"><font size="3">You can&nbsp;jump between Ubuntu&nbsp; LTS versions but if you are not on the LTS you 'd have to first update to the next Ubuntu version.<br />Be sure to fully update your current OS:</font><ul style="color:rgb(50, 50, 50)"><li><font size="3">sudo apt-get update</font></li><li><font size="3">sudo apt-get upgrade</font></li></ul><font size="3">Then try 'sudo apt install update-manager-core' to check for any broken dependencies<br />Fix any broken problems, usually by removing them and re-installing them.<br /><br /></font><ul style="color:rgb(50, 50, 50)"><li><font size="3">sudo shutdown -r now</font></li><li><span style="color:rgb(50, 50, 50)"><font size="3">Then, sudo&nbsp; do-release-upgrade</font></span></li></ul></div>]]></content:encoded></item></channel></rss>