- phenixbb - phenix-online.org

Phenix version 1.11.1 released
by Paul Adams 02 Nov '16

02 Nov '16

The Phenix developers are pleased to announce that version 1.11.1 of Phenix is now available (build 1.11.1-2575). Binary installers for Linux, Mac OSX, and Windows platforms are available at the download site: http://phenix-online.org/download/ Highlights for this version: New tools for omit maps without bulk solvent in omitted region, automated sharpening of cryo-EM and crystallographic maps, and segmentation of maps. Improved NCS search. New automated model-building tools for low-resolution maps - especially cryo-EM, tools for matching chains (both residues and direction), multiple improvements to phenix.real_space_refine and addition of new GUI. Improved model geometry restraints, many improvements to Phaser, improved validation incorporating new MolProbity features, simplified Rosetta installation, improved support for Amber, updated dependencies, Unicode support in GUI, new unified interface for atom selections. - General - Improved geometry restraints: - Conformation-Dependent Library for omega added (omega_cdl=True) - Installation - Rosetta installation centralised for phenix.rosetta_refine, phenix.mr_rosetta and ERRASER - Improved NCS search procedure with simplified parameters. Provides status of user-supplied NCS groups during validation (refused/modified/ok) - Updated dependencies - biopython 1.64 -> 1.66 - sphinx 1.2.2 -> 1.4.4 - ipython 2.1.0 -> 3.2.1 - pip 6.0.7 -> 8.0.2 - Neutron scattering tables: support ions - Amber refinement - Alpha release dev-2203 - GUI - New interfaces - phenix.map_comparison - phenix.polder - phenix.structure_search - phenix.real_space_refine - New selection editor - Unified interface for selecting atoms - Secondary structure annotations - NCS groups - TLS groups - Refinement strategy options - Unicode support - Non-ASCII characters are supported for most fields (e.g. file paths and job titles) - Using non-ASCII characters in projects/jobs will prevent earlier versions that do not have Unicode support from opening the project list correctly - Migrated validation after phenix.refine to use regular MolProbity for consistency (older versions of Phenix will not open new jobs) - phenix.real_space_correlation can now accept map files - phenix.molprobity can now accept map files - Updated dependencies for Linux - libpng 1.2.52 -> 1.5.26 - freetype 2.4.2 -> 2.6.3 - gettext 0.18.2 -> 0.19.7 - glib 2.12.11 -> 2.46.2 - expat 1.95.8 -> 2.1.0 - fontconfig 2.3.95 -> 2.11.1 - render 0.8 -> 0.11.1 - xrender 0.8.3 -> 0.9.7 - xft 2.1.2 -> 2.3.2 - pixman 0.19.2 -> 0.34.0 - cairo 1.8.10 -> 1.14.4 - pango 1.16.1 -> 1.38.1 - atk 1.9.1 -> 2.18.0 - libtiff 3.6.1 -> 4.0.6 - gtk+ 2.10.11 -> 2.24.29 - matplotlib 1.3.1 -> 1.5.1 - Maps - phenix.polder calculates omit maps which exclude the bulk solvent around the omitted region. This way, weak densities possibly obscured by bulk solvent may become visible. - phenix.model_map: Given PDB file calculate model map and output as CCP4 formatted binary map file. - phenix.mask: Given PDB file calculate bulk-solvent mask and output as CCP4 formatted binary map file. - phenix.auto_sharpen: Optimizes resolution dependence of a map to improve clarity - phenix.segment_and_split_map: Carries out segmentation of a map - Model-building - phenix.map_to_model builds models in low-resolution maps - builds any combination of RNA/DNA/protein - if NCS present, builds the asymmetric unit of NCS and expands to the entire map - phenix.segment_and_split_map breaks up a map into the asymmetric unit of NCS and further subdivides that into contiguous regions of density - phenix.chain_comparison compares CA or P atoms of two models and identifies how many residues match and how many are in the same direction - phenix.real_space_refine: - Support output of refined model in mmCIF format - ADP refinement runs by default at the last macro-cycle. Several CPUs can be used to speed up refinement: use nproc=NUMBER_OF_CPUs parameter for this. - phenix.model_idealization: tool to idealize model geometry while staying as close as possible to the starting model. Currently proteins only. Idealize covalent geometry and secondary structure, as well as eliminate rotamer and Ramachandran plot outliers, C-beta deviations. - phenix.geometry_minimization - ability to use reference torsion restraints - ability to use NCS constraints - phenix.phaser - SOLUTION HISTORY tracks solution through positions in RF/TF/PAK/RNP peak lists - selection by CHAIN and MODEL for PDB coordinate entry - automatic search number for single search ensemble - packing 'trace' molecule can be entered independently of coordinates and map - read TNCS/anisotropy binary files to avoid refinement, when running through scripts - write tNCS and anisotropy parameters to binary files (non-python interface) - default reading of I (or failing that, F) from mtz file (LABIN optional) - trace for ensembles from maps = hexgrid of 1000+/-100 points - trace for ensembles from coordinates above 1000 Calpha = hexgrid of 1000+/-100 points - trace for ensembles from coordinates twixt 1000 atoms and 1000 Calpha = Calpha atoms - trace for ensembles from coordinates under 1000 atoms = all atoms - packing by pairwise percent only, other packing modes obsoleted - packing test during FTF run by default with 50% pairwise packing cutoff - automatic tNCS NMOL determination in presence of commensurate modulation - added MODE GIMBLE, which splits ensembles by chain for rigid body refinement - support for unicode - solution coordinates placed nearest to input coordinates if possible - phenix.reduce - Updated reduce_wwPDB_het_dict as of Aug 12, 2016 - New script for updating het dict - Reduce no longer rotates methionine methyls by default. -DOROTMET flag reinstates old behavior - phenix.ramalyze - Improved handling of residue connectivity - Summary statistics provided for altloc A specifically where multiple altlocs present For a full list of changes see: http://www.phenix-online.org/documentation/CHANGES Please note that this publication should be used to cite use of Phenix: PHENIX: a comprehensive Python-based system for macromolecular structure solution. P. D. Adams, P. V. Afonine, G. Bunkóczi, V. B. Chen, I. W. Davis, N. Echols, J. J. Headd, L.-W. Hung, G. J. Kapral, R. W. Grosse-Kunstleve, A. J. McCoy, N. W. Moriarty, R. Oeffner, R. J. Read, D. C. Richardson, J. S. Richardson, T. C. Terwilliger and P. H. Zwart. Acta Cryst. D66, 213-221 (2010). Full documentation is available here: http://www.phenix-online.org/documentation/ There is a Phenix bulletin board: http://www.phenix-online.org/mailman/listinfo/phenixbb/ Please consult the installer README file or online documentation for installation instructions. Direct questions and problem reports to the bulletin board or: help(a)phenix-online.org and bugs(a)phenix-online.org Commercial users interested in obtaining access to Phenix should visit the Phenix website for information about the Phenix Industrial Consortium. The development of Phenix is principally funded by the National Institute of General Medical Sciences (NIH) under grant P01-GM063210. We also acknowledge the generous support of the members of the Phenix Industrial Consortium. -- Paul Adams Division Director, Molecular Biophysics & Integrated Bioimaging, Lawrence Berkeley Lab Division Deputy for Biosciences, Advanced Light Source, Lawrence Berkeley Lab Adjunct Professor, Department of Bioengineering, U.C. Berkeley Vice President for Technology, the Joint BioEnergy Institute Laboratory Research Manager, ENIGMA Science Focus Area Building 33, Room 347 Building 80, Room 247 Building 978, Room 4126 Tel: 1-510-486-4225, Fax: 1-510-486-5909 http://cci.lbl.gov/paul Lawrence Berkeley Laboratory 1 Cyclotron Road BLDG 33R0345 Berkeley, CA 94720, USA. Executive Assistant: Louise Benvenue [ LBenvenue(a)lbl.gov ][ 1-510-495-2506 ] --

1 0

phenix gui starting up for one, not for other users
by wtempel 01 Nov '16

01 Nov '16

Hello, we run phenix on a ubuntu 14.04 (x86_64) box. Phenix is installed in user x’s home directory. After running . ~x/prog/phenix-1.11.1-2575/phenix_env.sh; phenix, and some *setlocale* warnings, the phenix GUI will show up on the screen for user x. User y, after . ~x/prog/phenix-1.11.1-2575/phenix_env.sh; phenix, will get *setlocale* warnings, a white credit screen (briefly), but the GUI will not show up, but *phenix* does not exit. User does get the expected error messages after typing phenix.molprobity_1.11.1-2575 without specifying input coordinates, as does user y get the (older) GUI upon . ~x/prog/phenix-1.10.1-2155/phenix_env.sh; phenix. Do you have any suggestions as to how I can enable user y to use the 1.11.1 GUI? Thank you. Wolfram Tempel

2 4

postdoc jobs at Oxford
by Cell Guidance 01 Nov '16

01 Nov '16

Hello, May I please draw your attention to two excellent postdoc opportunities at the University of Oxford. Further information is available via the links below. Application deadlines are 30 November and 1 December 2016. Postdoc in Structural Biology: https://www.recruit.ox.ac.uk/pls/hrisliverecruit/erq_jobspec_details_form.j… Postdoc in Cell Biology: https://www.recruit.ox.ac.uk/pls/hrisliverecruit/erq_jobspec_details_form.j… Many thanks, Elena Dr. Elena Seiradake Dept. of Biochemistry, University of Oxford South Parks Road, Oxford, OX1 3QU, U.K.

1 0

Viewing different residues in the same location in Coot.
by Nigel Moriarty 28 Oct '16

28 Oct '16

Folks Phenix has the ability to refine two different amino acids (using alt. loc.) in the one place like in 1ejg. You can read more about it here. https://www.phenix-online.org/newsletter/CCN_2015_07.pdf#page=12 This crashes Coot until you add allow_duplicate_sequence_numbers() to $HOME/.coot.py in OSX or the appropriate place on Windows. For Windows, as there is no $HOME, Coot uses .coot.py or .coot-preferences/ directory for configuration - these can be found (added to) the directory in which Coot was installed (e.g. C:\WinCoot). Nigel PS While you're at it, why not add these lines below to automatically load FEM and polder maps. set_auto_read_column_labels("FEM", "PHIFEM", 0) set_auto_read_column_labels("mFo-DFc_polder", "PHImFo-DFc_polder", 1) --- Nigel W. Moriarty Building 33R0349, Molecular Biophysics and Integrated Bioimaging Lawrence Berkeley National Laboratory Berkeley, CA 94720-8235 Phone : 510-486-5709 Email : NWMoriarty(a)LBL.gov Fax : 510-486-5909 Web : CCI.LBL.gov

1 0

rosetta.build_phenix_interface errors
by Gerhard Fischer 28 Oct '16

28 Oct '16

I am having some trouble setting up phenix.rosetta_refine on my Kubuntu 16.04 LTS-system. I've been following the instructions found here: https://www.phenix-online.org/documentation/reference/rosetta_install.html The installation/compilation of Rosetta as such (rosetta_src_2016.37.58930_bundle.tgz) worked fine, and so did installing the latest version of Phenix - here, I've tried both the binary available for download (phenix-installer-1.10.1-2155-intel-linux-2.6-x86_64-centos6) and a self-compiled version (phenix-installer-1.11-2567-source). But when running rosetta.build_phenix_interface (both with nproc=6 or no multiple processor options set), the compilation crashes at some point. This takes quite a while, and I suspect most parts get compiled, but it does not run to completion. Any ideas? I attach the output of the error message below. Best wishes, Gerhard ------ stdout ---- g++ -o build/src/release/linux/4.4/64/x86/gcc/5.4/python/core/scoring/cryst/PhenixInterface.os -c -std=c++11 -ffor-scope -isystem external/boost_1_55_0/ -isystem external/ -isystem external/include/ -isystem external/dbio/ -pipe -Wall -Wextra -pedantic -Wno-long-long -Wno-strict-aliasing -march=core2 -mtune=generic -O3 -ffast-math -funroll-loops -finline-functions -finline-limit=20000 -s -Wno-unused-variable -Wno-unused-parameter -fPIC -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_SYSTEM_NO_DEPRECATED -DBOOST_MATH_NO_LONG_DOUBLE_MATH_FUNCTIONS -DPTR_STD -DNDEBUG -DWITH_PYTHON=1 -Isrc -Iexternal/include -Isrc/platform/linux/64/gcc/5.4 -Isrc/platform/linux/64/gcc -Isrc/platform/linux/64 -Isrc/platform/linux -Iexternal/boost_1_55_0 -Iexternal/libxml2/include -Iexternal -Iexternal/dbio -I/usr/include -I/usr/local/include -Iexternal/include/python2.7 src/core/scoring/cryst/PhenixInterface.cc src/core/scoring/cryst/PhenixInterface.cc: In member function 'void core::scoring::cryst::PhenixInterface::fitBfactors(core::pose::Pose&)': src/core/scoring/cryst/PhenixInterface.cc:253:34: error: no matching function for call to 'core::pose::Pose::dump_pdb(char [256], const char [2])' pose_asu.dump_pdb( pdbout , "1" ); ^ In file included from src/core/scoring/cryst/PhenixInterface.cc:18:0: src/core/pose/Pose.hh:1518:2: note: candidate: bool core::pose::Pose::dump_pdb(const string&) const dump_pdb(std::string const & file_name) const; ^ src/core/pose/Pose.hh:1518:2: note: candidate expects 1 argument, 2 provided src/core/pose/Pose.hh:1521:2: note: candidate: void core::pose::Pose::dump_pdb(std::ostream&) const dump_pdb(std::ostream & out) const; ^ src/core/pose/Pose.hh:1521:2: note: candidate expects 1 argument, 2 provided src/core/pose/Pose.hh:1525:2: note: candidate: void core::pose::Pose::dump_pdb(std::ostream&, const utility::vector1<long unsigned int>&) const dump_pdb( ^ src/core/pose/Pose.hh:1525:2: note: no known conversion for argument 1 from 'char [256]' to 'std::ostream& {aka std::basic_ostream<char>&}' src/core/scoring/cryst/PhenixInterface.cc: In member function 'void core::scoring::cryst::PhenixInterface::initialize_target_evaluator(const core::pose::Pose&, std::__cxx11::string)': src/core/scoring/cryst/PhenixInterface.cc:916:34: error: no matching function for call to 'core::pose::Pose::dump_pdb(char [256], const char [2])' pose_asu.dump_pdb( buffer , "1" ); ^ In file included from src/core/scoring/cryst/PhenixInterface.cc:18:0: src/core/pose/Pose.hh:1518:2: note: candidate: bool core::pose::Pose::dump_pdb(const string&) const dump_pdb(std::string const & file_name) const; ^ src/core/pose/Pose.hh:1518:2: note: candidate expects 1 argument, 2 provided src/core/pose/Pose.hh:1521:2: note: candidate: void core::pose::Pose::dump_pdb(std::ostream&) const dump_pdb(std::ostream & out) const; ^ src/core/pose/Pose.hh:1521:2: note: candidate expects 1 argument, 2 provided src/core/pose/Pose.hh:1525:2: note: candidate: void core::pose::Pose::dump_pdb(std::ostream&, const utility::vector1<long unsigned int>&) const dump_pdb( ^ src/core/pose/Pose.hh:1525:2: note: no known conversion for argument 1 from 'char [256]' to 'std::ostream& {aka std::basic_ostream<char>&}' src/core/scoring/cryst/PhenixInterface.cc: In member function 'void core::scoring::cryst::PhenixInterface::fitBfactors(core::pose::Pose&)': src/core/scoring/cryst/PhenixInterface.cc:244:25: warning: ignoring return value of 'int chdir(const char*)', declared with attribute warn_unused_result [-Wunused-result] chdir(tempdir_.c_str()); ^ src/core/scoring/cryst/PhenixInterface.cc:375:13: warning: ignoring return value of 'int chdir(const char*)', declared with attribute warn_unused_result [-Wunused-result] chdir(".."); ^ src/core/scoring/cryst/PhenixInterface.cc: In member function 'void core::scoring::cryst::PhenixInterface::initialize_target_evaluator(const core::pose::Pose&, std::__cxx11::string)': src/core/scoring/cryst/PhenixInterface.cc:914:25: warning: ignoring return value of 'int chdir(const char*)', declared with attribute warn_unused_result [-Wunused-result] chdir(tempdir_.c_str()); ^ src/core/scoring/cryst/PhenixInterface.cc:1080:13: warning: ignoring return value of 'int chdir(const char*)', declared with attribute warn_unused_result [-Wunused-result] chdir(".."); ^ src/core/scoring/cryst/PhenixInterface.cc: In member function 'std::__cxx11::string core::scoring::cryst::PhenixInterface::calculateDensityMap(core::pose::Pose&, bool)': src/core/scoring/cryst/PhenixInterface.cc:1100:25: warning: ignoring return value of 'int chdir(const char*)', declared with attribute warn_unused_result [-Wunused-result] chdir(tempdir_.c_str()); ^ src/core/scoring/cryst/PhenixInterface.cc:1109:13: warning: ignoring return value of 'int chdir(const char*)', declared with attribute warn_unused_result [-Wunused-result] chdir(".."); ^ scons: *** [build/src/release/linux/4.4/64/x86/gcc/5.4/python/core/scoring/cryst/PhenixInterface.os] Error 1 scons: building terminated because of errors. --------- stdout end ------ -- Gerhard Fischer, PhD Postdoctoral Research Associate University of Cambridge Department of Biochemistry 80 Tennis Court Road CB2 1GA Cambridge United Kingdom --- This e-mail message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail message and destroy all copies of the original message (including attachments).

2 1

Fix coordinates of one single residue
by ancacarl 28 Oct '16

28 Oct '16

Hi, I'm working on the refinement of a protein mutated with an unnatural amino acid that is present as two rotamers. Whenever I do refinements, one of the rotamers moves away from the electron density map. I therefore would like to fix the coordinates for this amino acid only while continuing the refinement of the rest of the protein. Is there a way in Phenix to do this? Any advice is welcome. Best regards, Anna-Carin

4 3

Fwd: Re: AW: phenix.real_space_refine
by Pavel Afonine 28 Oct '16

28 Oct '16

Hi Julia, > but I need to try different weightings to find the optimal one, so > this is not an option. no need to try different weights - the program does this for you automatically. If it doesn't - please report a bug. All the best, Pavel

1 0

GUP deadline approaching for APS Beamtime at NE-CAT
by Salbego, Cyndi 27 Oct '16

27 Oct '16

NE-CAT is accepting GUP proposals for the 2017-1 run cycle. Please choose 24-ID-C or 24-ID-E as your first choice to be scheduled with NE-CAT! The 24-ID-C beamline can deliver X-rays in the range of 6 to 21 keV or ~2.1 to 0.5 Å. This covers most of the popular elemental edges for phasing. This wide energy-range also makes the beamline well suited for ultra high-resolution data collection and soft X-ray sulfur SAD phasing. The beamline is equipped with an optional kappa goniometer for optimal alignment of crystals. A Pixel Array Detector (PAD), Pilatus-6MF, installed on the 24-ID-C beamline helps measure very weak Bragg reflection intensities due to its noise-less readout technology and also provides a very fast data collection capability in shutter-less data collection mode. The 24-ID-E beamline is a fixed energy microdiffraction beamline delivering X-rays at 12.66 keV, optimized for Se-SAD experiments. It is equipped with a CCD-based ADSC Quantum 315 detector. Both beamlines are equipped with state-of-the-art instrumentation to handle advanced data collection methods. MD2 microdiffractometers installed at both beamlines provide very clean beams from 5 microns to 100 microns in diameter and have exceptional sample visualization systems capable of visualizing micron-sized crystals with extreme clarity. Deadline Friday, October 28, 2016 for: - New General User Proposals (GUPs) - New Beam Time Requests for APS run 2017-1 (1/31/2017 - 4/24/2017) on existing active proposals - Partner user proposals (PUPs) - CAT Member Proposals - APS Beamline Staff Proposals - CAT Beamline Staff Proposals The GUP system (https://beam.aps.anl.gov/pls/apsweb/gup0005.start_page) will accept proposals and beam time requests until 11:59 pm (Chicago time) on October 28, 2016. However, User Office support will not be available after 5:00 pm that day. If you feel you may need help during the submission process, please create your proposal as early as possible. For questions about the GUP system or the proposal submission process, please contact gu_program(a)aps.anl.gov<mailto:[email protected]>. For guidance on the Proposal System, see https://www1.aps.anl.gov/Users-Information/About-Proposals/Concepts-Definit…. For general inquiries, please feel free to contact the User Office (630-252-9090, apsuser(a)aps.anl.gov<mailto:[email protected]>) Cyndi Salbego Administrator, NE-CAT 630.252.0689

1 0

tNCS
by Huyton, Trevor 25 Oct '16

25 Oct '16

Dear All, I have been struggling for while with a Molecular replacement problem for a large complex(3 proteins) with 2 copies per ASU. I have a small but 100% model for one of the components but this contributes only 12% of ASU (2 molecules) a much poorer <20% model that contributes the majority 80% of the ASU Space group is P222>P212121 best MR is in P21221. I have strong tNCS as seen in native patterson and phaser chooses this top peak in MR runs: There was 1 non-origin distinct peak (i.e. over 20% of origin peak and more than 15 angstroms from the origin) Sorted by Height ---------------- Height Distance Vector 56.0% 126.4 : FRAC +0.5000 +0.5000 +0.3500 (ORTH 63.0 88.0 65.4) Molrep also uses the same tNCS vector: --- Check Patterson for pseudo-translation --- PST_limit : 0.125 of origin peak INFO: pseudo-translation was detected. Origin Patterson peak: P,P/sig : 26479.002 239.412 1 Patterson peak : p,P/sig : 13591.399 122.888 2 Patterson peak : P,P/sig : 2506.590 22.664 3 Patterson peak : P,P/sig : 1517.345 13.719 Peak 1: trans.vector /ort/ : 62.995 88.023 65.691 trans.vector /frac/: 0.500 0.500 0.352 Peak 2: trans.vector /ort/ : 0.000 0.000 55.510 trans.vector /frac/: 0.000 0.000 0.297 Peak 3: trans.vector /ort/ : 58.238 88.023 65.730 trans.vector /frac/: 0.462 0.500 0.352 INFO: translation vector of peak 1 will be used. My question is how does this affect my MR with the smaller component? Is it exactly the same vector as the larger component? Thanks Trevor

1 0

Re: [phenixbb] phenix.real_space_refine
by Pavel Afonine 24 Oct '16

24 Oct '16

On 10/24/16 23:50, Pavel Afonine wrote: > I think "weight=1" may be a troublemaker.. It may be too far from > what's optimal (that program determines by default if you don't > specify any weight) and that may result in clashes that happen during > refinement. Of course, something else may cause this as well. > > Pavel > > On 10/24/16 20:07, Oleg Sobolev wrote: >> Hi Julia, >> >> In addition to Dorothee's response to your another e-mail, I would >> indeed recommend check the model geometry, in particular, bad atomic >> clashes (where 2 atoms are very close to each other). You can find >> them in the .geo file which should be created by this point or in >> log, under "Nonbonded interactions:". The worst clashes will be the >> first in the list. >> >> Best regards, >> Oleg Sobolev. >> >> On Mon, Oct 24, 2016 at 3:19 AM, Flis, Julia <julia.flis(a)charite.de >> <mailto:[email protected]>> wrote: >> >> Hello, >> >> my question is about the Phenix real space refinement. I am using >> the Phenix version phenix-1.11-2563. >> >> My command looks as follows: >> phenix.real_space_refine secondary_structure.enable=true >> Model.pdb VOL.map elbow.Model_pdb.001.cif Model.pdb_ss.eff >> resolution=3.8 weight=1 >> >> My problem is that the refinement suddenly stops during the first >> refinement cycle: >> >> >> >> Model_real_space_refined.log says: >> >> ********************** REFINEMENT MACRO_CYCLE 1 OF 5 >> ************************* >> ------------------------------------------------------------------------------- >> Update NCS operators >> ******************** >> ------------------------------------------------------------------------------- >> Update rotamer restraints >> ************************* >> ------------------------------------------------------------------------------- >> Global refinement >> ***************** >> END >> >> >> In the shell I get this : >> >> [...] >> distance: 184426 - 184921: 3.388 >> distance: 184428 - 184920: 3.342 >> distance: 184448 - 184898: 3.373 >> distance: 184449 - 184897: 3.187 >> distance: 184491 - 184860: 3.066 >> distance: 184531 - 184770: 3.203 >> distance: 184554 - 184746: 3.137 >> >> then it stops and the only files generated are >> Model_real_space_refined.log and Model_initial.geo. >> >> Could you give me an advise? I have no clue what the problem >> could be. >> >> Thank you, >> >> Julia >> >> >

1 0