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

How to run Spin Glass systems
by Hakob Abajyan 15 Jan '11

15 Jan '11

________________________________ Hi ALPS Team, I have investigated tutorials on ALPS web page but could not find any instructions how to run "classical Heisenberg spin-glass model" on ALPS. Could you please, answer to the following questions ? 1. Does ALPS support "classical Heisenberg spin-glass model" (Interaction constants are generated randomly) ? 2. If the answer of first question is positive, how to do that ? 3. Does ALPS support ensemble simulation or just simulation of one spin chain?Thanks in advance, Hakob

1 0

Fwd: [vistrails-dev] Announcing VisTrails 1.6
by Matthias Troyer 08 Jan '11

08 Jan '11

Begin forwarded message: > From: Emanuele Santos <emanuele(a)sci.utah.edu> > Date: January 7, 2011 9:03:34 PM GMT+01:00 > To: vistrails-users(a)sci.utah.edu > Cc: vistrails-dev(a)sci.utah.edu > Subject: [vistrails-dev] Announcing VisTrails 1.6 > Reply-To: vistrails-dev(a)sci.utah.edu > > Hello VisTrails users, > > Happy new year! > There is a new version of VisTrails available at http://www.vistrails.org/index.php/Downloads > > The release notes listed below contain a *very long* list of enhancements and bug fixes, so we would like to highlight the coolest ones: > > - A new Web Services package based on the SUDS (https://fedorahosted.org/suds/) library. Chapter 10 of the User's Guide was also updated with the new package. The old package will be removed on the next release, so please consider switching to the new package instead; > - Ability to save parameter explorations; > - Support for Workflow upgrades; > - VisTrails is now shipped with the ALPS (http://alps.comp-phys.org) package version 2.0.0rc5. > > As always, if you find any problems with this release let us know! > > Cheers, > > -- Emanuele Santos > VisTrails Developer > > -------------------------------------------------------------------------------------------------------- > RELEASE NOTES > > Release Name: v1.6 build e9f97c5908ac from v1.6 branch > > Enhancements: > - Added prompt for password for database access in batch mode (06c4b63434a7) > - Please notice that the parameter separator in the command line changed again from > '&&' to '$&$' so it's consistent with the server version. (35ad76515a97) > - VisTrails now has "Check for Updates" option in Help drop-down (b80862d8a39f) > - Show port_spec.sigstring in PortMismatch error message for more > detailed debugging (c28dad738abc) > - Turn off popup messages if messages window is open (62aeb9371235) > - add/delete Web Services from module palette for SUDSWebServices package (2e381a4394ed) > - Package-level context menus in the module palette (2e381a4394ed) > - Add preference for migrating tags and notes on upgrades (41177e74e687) > - Add stack trace to exception details for unexpected exceptions during > change_selected_version (fd3840df3c6b) > - Added new class Chdir to prevent users from triggering side-effects by accident > when using os.chdir() (4aa722db61d1) > - Added Open Recent to File menu (it works for vistrails in the file system or in > the database. The maximum number of files in the list can be configured from Advanced > Preferences Tab (search for maxRecentVistrails) (4aa722db61d1) > - Configuration object now supports bound methods as subscribers (4aa722db61d1) > - Debug messages now have a "details" attribute (f2911a6a6000) > - Buttons for filtering VisTrails messages (ebc728d49db3) > - Colors of message types added to theme file (ebc728d49db3) > - Improved log messages in the server log to also indicate the instance of the server that > is logging the messages (762902e79b7a) > - Improved handling of log messages (037568dc5960) > - Changed all examples using relative paths to datasets to use HTTPFile (403205442fd7) > - Updated head.vt and terminator.vt example to use TransferFunction widget (403205442fd7) > - Maintain suffixes on persistent files and directories (e9b5e906e069) > - Improved debug messages (9dcd1a5a2ea8) > - Ticket #390: Add support to Latex extension to download workflows at compilation > time (90ef6cee20a9) > - Improved error handling in vistrails.packages (a44800a88083) > - Improved debugging messages for vistrails.gui (25b718347ef0) > - Improved error handling in vistrails.core (2e095f36dc90) > - Debug library updated (41e3778d507e) > - Web Services package is now deprecated. Showing a warning message when the WebServices > package is loaded. Message will be shown only once. (9996bba52dd1) > - Ticket #375: Add GUI support for synchronizing vistrails (4efb09fbe5bd) > - Merge 2 Vistrails from within VisTrails (4efb09fbe5bd) > - Detect changes to directories so the cache can be invalidated when they change (3058d55966f2) > - New Web Services package that uses SUDS library (0d1d3efb99da) > - Add pinch gesture support to graphics views (3d01e549f849) > - ParaView package: Converted to new VisTrails package format (65453bd92aa5) > - Updated php scripts to work with Latex extension's new features (2b53ad32a374) > - VisTrails server: added new function to return version tree as pdf (2b53ad32a374) > - Created a separate php file to store the server configuration (8d15fdbe8e1d) > - Added support for running crowdlabs and vistrails server on separate machines > (still testing) (064304a99993) > - Ticket #382: Improvements to Latex extension (3123297d6a1b) > - LaTex extension: VisTrails can now embed a workflow graph or > a history tree in LaTex pdf (3123297d6a1b) > - LaTex extension: Caching latex instructions and images for embedding > images in case python is not available (3123297d6a1b) > - Ticket #381: Split HTTPFile.compute() method to download the file in a separate function (62d25dca3f3a) > - Add MplScatterplot and MplHistogram modules to pylab (4af6514c20d4) > - Ticket #295: Add Debug .command to Mac distribution (e835d69d8426) > - Added git executable to windows repository. It will be included > in future windows binaries for persistence package (8d9931bbbe04) > - Updated version of the rpy package (c895125216cb) > - Migrating new persistence package from persistence_exp to persistence (5b6418233dea) > - Added methods to expand shortcut string representations for module descriptors and port specs (5b6418233dea) > - Added support for shortcuts to remap modules/ports for upgrades (5b6418233dea) > - Use List for controlflow now instead of ListOfSElements (74f30460d3fe) > - Highlight invalidate port specs (74f30460d3fe) > - Improved support for work with the filesystem. Added DirectorySink module, > changed FileSink module to use 'overwrite' > instead of 'overrideFile', added support for getting the contents of a > directory, created a new OutputPath constant with a save-style widget > to select the output path, replaces OutputName on the FileSink module. > Added updgrade code to translate old FileSink module to new version. > Changed version of basic_modules and abstraction to static string > '1.6'. (fb30dca8a15d) > - HTTPFile now supports proxies. (3799edddbb62) > > Bug fixes: > - Fix issue with console mode and unit tests (a4d544eec673) > - Ticket #361: Cannot configure output cell layout for cells in groups in parameter > explorations (5807414236ba) > - Enable all spreadsheet cells for parameter exploration, even if they are embedded in > groups or subworkflows (5807414236ba) > - Ticket #399: Exception thrown when loading parameter exploration tab with no existing > exploration (4366e52c39cf) > - Fixed exception when loading parameter exploration tab for a workflow with no saved > explorations (4366e52c39cf) > - Ticket #154: vistrails should check for a new version being available and tell the > user to download it (b80862d8a39f) > - Ticket #398: Failure opening vtl files (filename issue) (c52ba7adc5f8) > - Matplotlib package: if hide toolbar parameter is set after the source > and there isn't an extra line at the end, the MplPlot would fail (c52ba7adc5f8) > - Ticket #398: Failure opening vtl files (filename issue) (cdfa0c97493d) > - Added escaping to filename in unzip commandline call (cdfa0c97493d) > - Fixed issue where it was not possible to ungroup a subpipeline that had an InputPort > connected directly to an OutputPort (e1ea9b437507) > - Fixed problem where controlflow package would raise duplicate errors (4351b3f0102f) > - Fixed issue with groups and input values that evaluate to False (6fc007c0535d) > - Fixed ordering of PortMismatch parameters in ensure_port_specs (c28dad738abc) > - Fixed bug introduced on Windows platforms when changed os.chdir() calls by > core.utils.Chdir (0a2b8a0d50d8) > - Enable the Linux theme for 'Linux' system types (57dfb4a85e7a) > - added deletion of namespaces in module palette (2e381a4394ed) > - Add ability to migrate tags when upgrades are not delayed (9c49285269ca) > - Message filter colors does not show in linux (ee8906c91039) > - Ticket #397: Save execution log when in console mode (2dae96a8f004) (1afa51d895e9) > - Update version tree when adding delayed actions (d1dbf3005499) > - Subworkflows from packages that need upgrades are now moved to local.abstractions > in the registry and picked up for workflow upgrades (04476a172f61) > - Fixed issue with spreadsheet and grouped spreadsheet cells (fd3840df3c6b) > - Replaced svn command with git command to get current commit (if present) (4aa722db61d1) > - Flush delayed actions (including upgrades) to fix issues with delayed upgrades and > grouping upgraded workflows (79dd982e6cef) > - VisTrails Server: Applied fix to caching of history tree images when > generated as pdfs (fc0ab9f1626d) > - VisTrails Server: fixed problem in caching of history tree images (4862e1f7d18a) > - Ignoring mouse gestures when Qt version is < 4.6 (4862e1f7d18a) > - Ticket #394: VisTrails server is not detecting updates in vistrails loaded > from the database (762902e79b7a) > - Restoring extensions/http/run_vistrails.php to version before merge (762902e79b7a) > - VisTrails server was ignoring the build_always variable if it > found cached images (762902e79b7a) > - Using port to identify the instance of the server instead of virtual > display in script that starts vistrails server using Xvfb (762902e79b7a) > - Ticket #393: Latex extension doesn't handle workflow exec. errors properly (16f522c459c5) > - Latex extension: Making sure to convert line breaks into \MessageBreak > Latex commands before displaying error messages. (16f522c459c5) > - Forwarding force build to server so the server can also bypass > caching (47a1105664a0) > - Ticket #392: Refactor php extensions caching logic used for wf executions (3125e0eb8e81) > - Updated mediawiki extension to work with crowdlabs server (3125e0eb8e81) > - Added workaround for RotateFileHandler problem on Windows when some > packages start child processes during workflow execution (e5afc47797cb) > - Fixed issue where named intermediate persistent files/directories were not > reused correctly (df3deb58a18c) > - Fixed git hash retrieval for persisted directories (df3deb58a18c) > - Pasted text in VisTrails shell was being ignored (c48e67f02ae8) > - Giving focus to VisTrails shell when showing it (c48e67f02ae8) > - Added 'VisTrails messages' button and fixed 'VisTrails debugger' button (b401b2498c74) > - Don't mask AttributeErrors when materializing pipelines (b5c3650e5ca6) > - Add upgrade path for old InputPort and OutputPort modules (8abfff56592c) > - Fixed an issue with groups and upgrades (720d93c8e3be) > - VisTrails shell was not using fixed-width font (b521e096f879) > - Latex extension: delaying check for a valid url so we can include > cached images if there's no Internet connection (79296270cc86) > - Batch mode: On Windows, VisTrails was not executing workflows > when an absolute path to a vt file was given (81812ac04e85) > - Minor error fixes (45b53eef1c53) > - Ticket #386: Moving modules after an upgrade generates invalid actions with > delayed upgrades (ad9e029035f7) > - With delayed upgrades, moving modules after an upgrade now generates actions > in the correct order (ad9e029035f7) > - Ticket #385: Workflow instantiation fails when doing on-demand package loading (aff3408c7a51) > - Fix issue with on-demand package loading leaving workflows as invalid (aff3408c7a51) > - Casting DBLocator names to string as they can store None sometimes (9996bba52dd1) > - Ticket #384: Deleting version edits version tag if delete is canceled (cc05bc9e80e5) > - Don't delete tag text when attempting to prune (cc05bc9e80e5) > - Expanding port specs deals with differences between descriptor and port signatures (c5763a437606) > - UpgradeWorkflowError tries to trim None-value (93b3be3d2a50) > - Ticket #383: Unversioned modules are not upgraded (4b3fa72869f0) > - If a module has no version, force it to be upgraded (4b3fa72869f0) > - Ticket #302: Moved modules action generated when nothing changed (3e59defe4685) > - Fixed logic so moved modules are properly detected and positions updated. (3e59defe4685) > - ParaView package: Removed hardcoded path to pvserver and mpiexec > and using configuration object for that (accessible through Menu > Preferences -> Module Packages) (65453bd92aa5) > - ParaView package: Updated pv.vt example to work with current version > of the package (65453bd92aa5) > - Fixed bug in some php scripts when only the tag is passed instead of > a version number (2b53ad32a374) > - Updated all php scripts in extensions/http to work with > the current version of crowdlabs vistrails server (only local > setup currently supported) (8d15fdbe8e1d) > - Fixed bug where server method get_wf_graph_png would sometimes > fail (064304a99993) > - Fixed bug where although DBLocators were being cached, the > connections were not (b07c22d9e93d) > - Ticket #359: When using VTKRenderOffscreen module VisTrails crashes (48e477f4c1d9) > - VTK Package doesnt work with VTK version 5.7.0 (ba5e0bdbbb16) > - Fixed issue with query-by-example where parameters couldn't be updated (741b1c0d7737) > - Error using breakpoint due to new stack trace (d4f31af05a05) > - LaTex extension: removed hardcoded url for downloading vt files > upon clicking on the images in the generated pdf. It can now be set using > the \vistrailsdownload in the latex file (3123297d6a1b) > - HTTP package was not handling exceptions correctly (62d25dca3f3a) > - Ticket #380: HTTPFile corrupts binary files on Windows (0a5ec2007878) > - Color Constant: Initializing Color widget with default white > color using RGB constructor instead of QtCore.Qt.White. We assume the > color is always a QColor object and sometimes a GlobalColor object > was being found (8565a276a353) > - Persistence Package: Added code to find tar executable similar > to the way the path to git is set up (4a2494c09ef4) > - Persistence Package: adapted use of tar command to work > on Windows (430e29bcaf2e) > - Windows binary: Including the gnu version of tar instead > of the one that comes with git (430e29bcaf2e) > - Set MplFigureCell to fill spreadsheet cell (4af6514c20d4) > - Ticket #302: Moved modules action generated when nothing changed (8f60ea9a4737) > - Dangling move actions are displayed immediately after switching versions (8f60ea9a4737) > - Ticket #331: ImportError when trying to import userpackages (bc27cdc4b171) > - "import userpackages" fixed by reordering init steps (bc27cdc4b171) > - Ticket #293: Shell copy & paste on Mac doesn't work (694c0a43fbda) > - Use git ls-files instead of cat-file to retrive hash so that we don't have issues with Windows reading from stdin (1b190225cce9) > - Persistence package: fixed problem where persistent files > couldn't be found on Windows (df8a7c2ef7d1) > - Ticket #369: picture-in-picture setting is confused when a new vistrail is opened (7ea68b3e863f) > - Check PIP preference when opening vistrails (7ea68b3e863f) > - Allow semi-translation from abstractionRef to abstraction so > old workflows (version <= 0.9.3) with subworkflows can be opened (50b9ce2b28fc) > - Spreadsheet: fixed 'RuntimeError: underlying C/C++ object has > been deleted' problem during EventFilter on Windows (93884b6a47c0) > - VTK Package: Fixed rendering context problem when embedding VTKCell in VisMashup on Linux (93884b6a47c0) > - PathChooserToolButton was not emitting proper signals necessary for > VisMashup (93884b6a47c0) > - Persistence package: Fixed load package error on Windows (4ee8f244fc79) > - Change persistence package to use correct identifier for gui widgets (9dd3ad8e0b08) > - Ticket #378: Workflow execution log contains duplicate entries (6d65daec6089) > - Fixed logging so that executions are not duplicated when saving more than once per session (6d65daec6089) > - Ticket #377: Exporting to OPM XML fails (3ee1cc842182) > - Fixed OPM output capability to work with latest object layout (3ee1cc842182) > - Update sql package to use List instead of ListOfElements (4b08dd9018db) > - Fix typo with get_package_by_name (74f30460d3fe) > - keep selected modules after scene redraw (bb5e4e6e1f45) > - Optional input ports now don't show up as output ports (bb5e4e6e1f45) > - Ticket #376: execute_cmdline broken (bbbcf19704b8) > - Fixed copyright year in background image from About box (bcd3346d8865) > - Web Services package: fixed bug in certain Complex Types (60128ff3a89a) > - Ticket #374: Web service package can't be reloaded (38976729a2a9) > - Fixed an issue with package reloading where modules imported using the "from" syntax were not added to the imported list (38976729a2a9) > - HTTPFile: Fixed error when parsing the date from the file's > header. (3799edddbb62) > > >

1 0

Worm algorithm for classical XY-like models
by Austen Lamacraft 05 Jan '11

05 Jan '11

Dear ALPS community, We are interested in studying a generalized classical XY model containing both cos(theta_i-theta_j) and cos(2(theta_i-theta_j)) terms. I have a couple of questions: 1. Is it possible to do classical worm simulations using (perhaps a simple modification of) the QMC worm code? 2. If so, can a term like cos(2(theta_i-theta_j)) be specified in the quantum mode, where it corresponds to pair hoppng? Many thanks, Austen Lamacraft

1 0

stiffness?
by Xiao Quan Yu 27 Dec '10

27 Dec '10

Dear all, I am now studying the 3D bose glass model. I got some confusions about the stiffness. By using SSE, I got the stiffness is 2.2427 from the following setting: LATTICE_LIBRARY="lattices.xml"; LATTICE="inhomogeneous simple cubic lattice"; L=5; MODEL_LIBRARY="models.xml"; MODEL="hardcore boson"; t = 1.0; T = 0.1; delta=10.0; SWEEPS=500000; THERMALIZATION=10000; EPSILON=0.25; { DISORDERSEED = 34275; mu=delta*2*(random()-0.5); } My question is: if this stiffness is rescaled one, namely ρs*L^4=2.2427 ? The power 4th is from Fisher argument. Thank you in advance! Best, Xiaoquan ---------------------------------------------------------------- SISSA Webmail https://webmail.sissa.it/ Powered by SquirrelMail http://www.squirrelmail.org/

2 1

Re: [ALPS-users] what is the prefactor of stiffness?
by Fan Xiao 23 Dec '10

23 Dec '10

As my understanding, the "stiffness" extracted is actually (rho*L^{d-1}) for square lattice or 3d simple cubes. The real one should be 2.2427/5 in your case. But I have a question about the stiffness as well. I used a 8x8x2 lattice, how is the simulated "stiffness" related to the actual one? (if it is 8x8x8, I know it is rho*8, but this is not a simple cubic, is there an expression to calculated it?)

2 1

Fw: anisotropic Heisenberg model setup
by Ruben Ghulghazaryan 22 Dec '10

22 Dec '10

Hi Ryo IGARASHI, First of all I would like to thank ALPS team for your collaboration and support. Thanks for your comments and explanations. Please find my questions below. Thanks, Ruben ________________________________ From: Ryo IGARASHI <rigarash(a)hosi.phys.s.u-tokyo.ac.jp> To: comp-phys-alps-users <comp-phys-alps-users(a)lists.phys.ethz.ch> Sent: Tue, December 21, 2010 2:12:40 AM Subject: Re: [ALPS-users] anisotropic Heisenberg model setup Hi, Ruben, On Mon, Dec 20, 2010 at 8:36 PM, Ruben Ghulghazaryan <ghulr(a)yahoo.com> wrote: > By anisotropic model on a ladder I mean that we have two different > interaction terms in Hamiltonian as shown in the file attached. Thus we have > two bond types "0" and "1" in horizontal and vertical directions and we want > to have different interaction terms in horizontal and vertical directions. This is usual setting, I believe. [Ruben]---> Yes. > As far as I understand, according to "spin" model definition J0 parameter > should be for bond type="0" and J1 for bonds type="1". This is correct. [Ruben]---> OK. > If we set J=1 only then (even if J1=0) all bonds irrespective of their type > should get 1 as bond term, don't you? This is simply wrong. J=1 just means J0=1. As Matthias said, all the J1 term is 0 (J1=Jz1=Jxy1=0) when only J=1 is set. [Ruben]--->OK. Does it mean that all bond interaction terms will be the same both in horizontal and vertical directions? Or, does it mean we have only horizontal bonds with interaction J0=1 and vertical bonds terms = 0 and we have two non-interacting chains instead of a ladder? > In the case we specify J0=1 and J1=1 again all bonds should get 1 as bond > term and the model results should be the same > as for setting J only. In this case both isotropic and anisotropic models > should give similar results. J0=1 and J1=1 give the symmetric ladder. And thus, you will get the same results if you specify a symmetric ladder (i.e. all coupling constant is same IN THE LATTICE DESCRIPTION) with J=1. [Ruben]---> I agree and this is what I expect too. I did an experiment with the following settings which as far as I understand both should set the same bond interaction term 1 for all bonds: (a) LATTICE="ladder" MODEL="spin" local_S = 1 J = 1 CONSERVED_QUANTUMNUMBERS="Sz" {L = 4} ++++++++++++++++++++++++ (b) LATTICE="ladder" MODEL="spin" local_S = 1 J0 = 1 J1 = 1 CONSERVED_QUANTUMNUMBERS="Sz" {L = 4} ========================== I run fulldiag then fulldiag_evaluate fulldiag parm1.in.xml fulldiag_evaluate --T_MIN 0.1 --T_MAX 10 --DELTA_T 0.1 parm1.task1.out.xml The results of these two runs are different. I can not understand why the results should be different. Does (a) defines a ladder were both horizontal and vertical bond terms are equal 1? Does (b) defines a ladder were both horizontal and vertical bond terms are equal since J0=J1=1? Please see the file attached for illustration. If these two parameter files use different settings but define the same lattice and model, then why the results of fulldiag runs are different? Please let me now if you need more data. Thanks! -- Ryo IGARASHI, Ph.D. rigarash(a)hosi.phys.s.u-tokyo.ac.jp OpenPGP fingerprint: BAD9 71E3 28F3 8952 5640 6A53 EC79 A280 6A19 2319

2 2

anisotropic Heisenberg model setup
by Ruben Ghulghazaryan 21 Dec '10

21 Dec '10

Hi ALPS team, I am trying to make simple simulations with anisotropic Heisenberg model on a ladder with ALPS2 rc2. According to models.xml and full diagonalization web page if I specify J0 and J1 parameters then for different bond types "0" and "1" I will have J0 and J1 coefficients in Heisenberg ("spin") model. I did a simple experiment by performing fulldiag two simulations: one by using J=1 and the other J0=1,J1=1 and compared the results. I expected that the results should be the same according to "spin" model definition: defaults for J0and J1 is J if they are not specified. But I found that the results of energy and other quantities are different. below are my two parameter files: LATTICE="ladder" MODEL="spin" local_S = 1 J = 1 CONSERVED_QUANTUMNUMBERS="Sz" {L = 4} ++++++++++++++++++++++++ LATTICE="ladder" MODEL="spin" local_S = 1 J0 = 1 J1 = 1 CONSERVED_QUANTUMNUMBERS="Sz" {L = 4} ========================== I run fulldiag then fulldiag_evaluate fulldiag_evaluate --T_MIN 0.1 --T_MAX 10 --DELTA_T 0.1 parm6a.task1.out.xml as given in the web page http://alps.comp-phys.org/mediawiki/index.php/ALPS_2_Tutorials:ED-06_FullDi… Would you please help me to understand why the results are different? Thanks, Ruben

4 10

what is the prefactor of stiffness?
by Xiao Quan Yu 14 Dec '10

14 Dec '10

Dear all, I am now studying the 3D bose glass model. By using SSE, I got the stiffness is 2.2427 from the following setting: LATTICE_LIBRARY="lattices.xml"; LATTICE="inhomogeneous simple cubic lattice"; L=5; MODEL_LIBRARY="models.xml"; MODEL="hardcore boson"; t = 1.0; T = 0.1; delta=10.0; SWEEPS=500000; THERMALIZATION=10000; EPSILON=0.25; { DISORDERSEED = 34275; mu=delta*2*(random()-0.5); } My question is: why this stiffness is larger than one? Is there some scaling prefactor in front? Thank you in advance! Best, Xiaoquan ---------------------------------------------------------------- SISSA Webmail https://webmail.sissa.it/ Powered by SquirrelMail http://www.squirrelmail.org/

2 1

Can the DMRG packet of ALPS calculate the finite temperature problem?
by Chen Ahai 13 Dec '10

13 Dec '10

dear all my question just as title. thank you -- -------------------------------------------------------------------------- Chen Ahai Department of Physics, Zhejiang Normal University Jinhua, Zhejiang Province, 321004, China e-mail: chenahaiphysics(a)gmail.com; chenahai(a)yahoo.cn

2 2

ALPS 2.0.0rc4 packages for Debian (amd64)
by Ryo IGARASHI 13 Dec '10

13 Dec '10

Hi, all, As always, I have created binary packages of ALPS 2.0.0rc4 for Debian GNU/Linux (sid/unstable) for amd64. The apt line is as follows: deb http://alps.comp-phys.org/static/software/debian/sid ./ deb-src http://alps.comp-phys.org/static/software/debian/sid ./ The largest change from previous versions is 'dirloop_sse'. As dirloop_sse do not depend upon lp_solve any more, I can easily include it in the package. If you find any problems regarding this package, please let me know. Best regards, -- Ryo IGARASHI, Ph.D. rigarash(a)hosi.phys.s.u-tokyo.ac.jp OpenPGP fingerprint: BAD9 71E3 28F3 8952 5640 6A53 EC79 A280 6A19 2319

1 0