May 2020 - Comp-phys-alps-users - lists.phys.ethz.ch

Re: [ALPS-users] DWA - which version / compiled is needed
by Tama MA 28 May '20

28 May '20

Hey Lode, Really nice to hear from you! It has been ages! Answers inline. > On 26 May 2020, at 2:13 PM, Lode Pollet <Lode.Pollet(a)physik.uni-muenchen.de> wrote: > > hi Tama, > > how are you? We are having a difficult year :) Business-wise, trading execution services are fine. - HK exchange is still functioning. Political-wise, we are facing more squeeze from Beijing :( > > I've been thinking about a light version migrated to ALPSCore for some time but never started doing it although it would be a good time to clean up the code again. Based on my existing code this would not take too long. I have enough experience with ALPSCore for that. ALPSCore does not incorporate the applications so it is independent of a worm algorithm code. > It would only be for Bose-Hubbard and (in-plane ferromagnetic) spin models on very simple lattices. Visualization should be split again from the core code, as this (for us) is an application from the past. > There are too many parts of this code that are model-dependent (nowadays it is always a variant of those models that you need to simulate, but it requires some small changes to the code), > and that makes me hesitant because I am not sure it will be that useful. So this is why I think that something light and flexible is better. > I need your help (and Matthias’s help) for the physics. I already lost touch with physics. Regarding integration into current middleware / virtualization, I would be happy to help. We just need to have a plan to spend this amount of man-days to implement this change. Maybe Matthias has a bigger plan for this? > I don't know about Kafka or elasticsearch. > What do you have in mind on native ETL support for big data infrastucture? Elasticsearch - for fast-search NoSQL DB (Really fast for non-aggregated search). Kafka - for real-time ETL streaming. If you need lower-latency, then you need gRPC + Protobuf. That’s another story. (We don’t want to invest in building such framework.) > Do you see any bottlenecks currently? > Not for me. Regarding DWA, that was developed in 2012 with GCC-4.x. We know that it would be supported till 2024 by RHEL-7. (10 years promise by Redhat) We still have 4 years left to implement the migration :) There is still some time. > But anyone can send me their wishlist or suggestions and then I will see what I can do (but not before Corona times are over). You can also join if you wish, then I will set up a git or so. > > lode > > > > > >> On 26. May 2020, at 04:22, Tama MA <tamama(a)yotcopi.com> wrote: >> >> Containerize ALPS-DWA ? >> >> - To maintain DWA further requires some effort. >> - One simple option would be to containerize DWA of course. With podman / runc in RHEL-8, this overhead is almost negligible. >> - Other virtualization option include conda. >> >> I must admit that at the time DWA was written, we were at a different era. If given the time for another PhD with Matthias ( :) ), I would revamp this design to incorporate Kafka and Elasticsearch (++) - that supports built-in visualization and native-ETL support for modern big-data infrastructure. >> >> The question now is really whether this code is worth our effort to improve further? >> (I wrote DWA, so I would be the best person to be assigned this task…) >> >> Well, I leave this question to the community, and Matthias would have a bigger vote :) >> >> If yes, how many man-days would we assign to this task? >> >> Kind regards, >> Tama MA >> >> >> >> >>> On 26 May 2020, at 12:41 AM, Mateusz Łącki <mateusz.lacki(a)gmail.com> wrote: >>> >>> Hi, >>> I want to compile DWA from source on Linux. As far as I know "old" DWA >>> verions from ALPS 2.2 work fine, but require ancient GCC (gcc at most >>> 5.5). Newer DWA from ALPS 2.3 compiles ok with some of new compilers >>> (at the very least with clang), but it quickly crashes with >>> segmentation fault (Oskar Prosniak email from from 22/02/2018). >>> >>> The problem is that it is not so easy to install gcc on a new machines >>> these days, as gcc5 uses some deprecated header files which have been >>> removed from glibc 2.28 and newer (ustat.h). Downgrading glibc is not >>> really an option. >>> >>> Is there any option these days to compole any version DWA from source, >>> preferably 7650 (with the intent of make a few small changes to the >>> source code) in such a way the updated DWA code can be deployed eg. on >>> cluster (that is without using old linux distribution, without >>> downgrading glibc, and preferably without gcc-5). >>> >>> ?? >>> >>> Best, >>> Mateusz Łącki >>> >>> >>> ---- >>> Comp-phys-alps-users Mailing List for the ALPS Project >>> http://alps.comp-phys.org/ >>> >>> List info: https://lists.phys.ethz.ch//listinfo/comp-phys-alps-users >>> Archive: https://lists.phys.ethz.ch//pipermail/comp-phys-alps-users >>> >>> Unsubscribe by writing a mail to comp-phys-alps-users-leave(a)lists.phys.ethz.ch. >> >> >> >> ---- >> Comp-phys-alps-users Mailing List for the ALPS Project >> http://alps.comp-phys.org/ >> >> List info: https://lists.phys.ethz.ch//listinfo/comp-phys-alps-users >> Archive: https://lists.phys.ethz.ch//pipermail/comp-phys-alps-users >> >> Unsubscribe by writing a mail to comp-phys-alps-users-leave(a)lists.phys.ethz.ch. >

3 7

DWA - which version / compiled is needed
by Mateusz Łącki 26 May '20

26 May '20

Hi, I want to compile DWA from source on Linux. As far as I know "old" DWA verions from ALPS 2.2 work fine, but require ancient GCC (gcc at most 5.5). Newer DWA from ALPS 2.3 compiles ok with some of new compilers (at the very least with clang), but it quickly crashes with segmentation fault (Oskar Prosniak email from from 22/02/2018). The problem is that it is not so easy to install gcc on a new machines these days, as gcc5 uses some deprecated header files which have been removed from glibc 2.28 and newer (ustat.h). Downgrading glibc is not really an option. Is there any option these days to compole any version DWA from source, preferably 7650 (with the intent of make a few small changes to the source code) in such a way the updated DWA code can be deployed eg. on cluster (that is without using old linux distribution, without downgrading glibc, and preferably without gcc-5). ?? Best, Mateusz Łącki

2 2

dwa - missing output when tunneling is increased
by Mateusz Łącki 25 May '20

25 May '20

Dear All, I am using the following code (file anal.py) to read ALPS results. When I run the simulation using run.py (v1) (file below), then I am getting some result, when I am using run.py (v2) then I am getting no results and output file read error. The v1 and v2 of run.py differ by a single byte: in v1 the boseHubbard hopping in 0.02 while in the other it is 0.2. lattice.xml and models.xml are standard files (I planned to change them, but first I wanted some test data from a starndard BH). Does anyone know what I am doing wrong? I am using alps revision 7650. Best, Mateusz Łącki ************************************ anal.py *************** import pyalps bin_dir = '/nfs/andy2/home/lacki/alps/install22b4/bin/' # Setting graphical output import matplotlib as mpl mpl.use('agg') # Evaluating the simulation and preparing plots using Python import pyalps import matplotlib.pyplot as plt import pyalps.plot as aplt results = pyalps.getResultFiles(prefix='parm1a') print(results) data = pyalps.loadMeasurements(results,what=['Local Density^2',]) rhos = pyalps.collectXY(data,x='t',y='Local Density^2') print('rhos',rhos) *************************************************************************** ************************************ run.py (v1) *************** import pyalps bin_dir = '/nfs/andy2/home/lacki/alps/install22b4/bin/' parms = [] for t in [0.02, ]: parms.append( { 'LATTICE_LIBRARY' : "lattices.xml", 'MODEL_LIBRARY' : "models.xml", 'LATTICE' : "square lattice", 'MODEL' : "boson Hubbard", 'T' : 0.1, 'L' : 4 , 't' : t , 'mu' : 0.5, 'U' : 1.0 , 'Nmax' : 5 , 'THERMALIZATION' : 10000, 'SWEEPS' : 2000000, 'SKIP' : 10, 'MEASURE[Winding Number]': 1, 'MEASURE[Local Density^2]': 1, 'RESTRICT_MEASUREMENTS[N]': 16 } ) input_file = pyalps.writeInputFiles('parm1a', parms) res = pyalps.runApplication(bin_dir+'dwa', input_file, Tmin=5, writexml=True) ************************************************************** ************************************ run.py (v2) *************** import pyalps bin_dir = '/nfs/andy2/home/lacki/alps/install22b4/bin/' parms = [] for t in [0.2, ]: parms.append( { 'LATTICE_LIBRARY' : "lattices.xml", 'MODEL_LIBRARY' : "models.xml", 'LATTICE' : "square lattice", 'MODEL' : "boson Hubbard", 'T' : 0.1, 'L' : 4 , 't' : t , 'mu' : 0.5, 'U' : 1.0 , 'Nmax' : 5 , 'THERMALIZATION' : 10000, 'SWEEPS' : 2000000, 'SKIP' : 10, 'MEASURE[Winding Number]': 1, 'MEASURE[Local Density^2]': 1, 'RESTRICT_MEASUREMENTS[N]': 16 } ) input_file = pyalps.writeInputFiles('parm1a', parms) res = pyalps.runApplication(bin_dir+'dwa', input_file, Tmin=5, writexml=True) **************************************************************

1 1

Unable to run looper QMC simulation
by Michelle 18 May '20

18 May '20

2 1