kwip

About

Username
kwip
Joined
Visits
369
Last Active
Roles
Member

Comments

  • I'd suggest to install msys2 and follow Guidos installation guide. Instead of arpack I'd go with arpack-ng and along with this with openblas. A quite nice guide on how to start I found recently is http://www.math.ucla.edu/~wotaoyin/windows_codi…
  • Yes, I did. @edit I did not read properly. I'm using msys2 to compile ccx, here you can install openblas as precompiled binary. arpack-ng properly configures. When compiling ccx one points to spooles, arpack-ng and the system openblas. quite strai…
    in CCX 2.13 Comment by kwip December 2017
  • I've rebuilt ccx from scratch with a generic tune ... in parallel I cleaned up github. The binary uses arpack-ng and openblas. I hope it runs well and on all 64bit cpus. regards
    in CCX 2.13 Comment by kwip December 2017
  • thx mate, thx for kind words. I'm happy you got a working binary. To find a solution for a problem is as rewarding as winning in sports or on the race track.
    in CCX 2.13 Comment by kwip December 2017
  • great to hear. The environment was not the problem. My Laptop is sporting a i7-6820HK from 2015. Your i7 860 is from 2009. I compiled my binary with the most recent gcc/gfortran using "-mtune=native" which uses "all" available optimization and instr…
    in CCX 2.13 Comment by kwip December 2017
  • @Hengre give it a try with: ccx_2.13_MT_apng_gen.exe regards
    in CCX 2.13 Comment by kwip December 2017
  • I'll create a binary without a CPU specific tune to test asap. Maybe the mtune and march flags introduce an issue. Otherwise I have no idea ...
    in CCX 2.13 Comment by kwip December 2017
  • the builds are fully static, no external libs are required. They are 64bit only. Did you try to save your model as inp to run it via windows-cmd? regards
    in CCX 2.13 Comment by kwip December 2017
  • I was comparing apples and oranges ... no env impact ... a ran an input deck with abaqus for reference ... here, I had to use S8R anyway. So I accidentally replicated Andrea's results I successfully compiled CCX with arpack-ng, no improvement. So…
    in CCX 2.13 Comment by kwip December 2017
  • I did some research finding other projects having issues with ARPack which is kind of EOL. ocatve, scilab were forking their own implementation. There is some effort of consolidation, namely arpack-ng. I'll try to build CCX against this arpack versi…
    in CCX 2.13 Comment by kwip December 2017
  • So we have to dig into arpack. Anyway, first I'll figure out how and why the environment can change the result of CCX
    in CCX 2.13 Comment by kwip December 2017
  • I could not wait and I have found a strange issue. Try to save the job as inp and run the ccx_2.13_MT.exe directly at the input-deck. then check the dat file ... Now capture the mecway ccx run by a simple wrapper in as ccx.bat file to be used inste…
    in CCX 2.13 Comment by kwip December 2017
  • unfortunately this is a known issue. I did not investigate it in depth, but it might be indruduced by CCX expanding shells to solids. Could you please provide the liml file so I can check if ccx on Windows behaves the same a ccx on Linux? Chrismas …
    in CCX 2.13 Comment by kwip December 2017
  • thanks mate, no problem, maybe I got caught on the wrong foot a bit regards
    in CCX 2.13 Comment by kwip December 2017
  • kind of strange ... I recompiled it with different settings. I previously forced the compiler to include libwinthread, maybe here Windows Defender got upset ... thanks for testing and some positive feedback ... maybe a PM would serve the same purpos…
    in CCX 2.13 Comment by kwip December 2017
  • I could not wait and did some quick tests. On my windows 10 machine everything runs well.Simon, which  kind of system do you use? My binaries are intended for 64bit only. Which processor type do you use? Maybe my "-mtune=native" breaks the binary fo…
    in ccx 2.12 Comment by kwip April 2017
  • I have to admit I compiled them as usual without testing them afterwards. I will do these checks on the next weekend providing updated executables if required. Sorry for any inconvenience.
    in ccx 2.12 Comment by kwip April 2017
  • thanks andrea, I will dig into this on the next weekend ... I assume this will require some more time
    in ccx 2.12 Comment by kwip April 2017
  • maybe a small addition for the ones compiling as well: non-opt: spooles, arpack and  ccx are compiled with -O0 opt: spooles, arpack and ccx are compiled with "-O2 -mtune=native -march=native"
    in ccx 2.12 Comment by kwip April 2017
  • CCX 2.12 is out, I will compile a non-optimized version and an optimized one, let's see if there is a difference.
  • In almost all cases elements of type C3D20R are the Elements of choice. Stress gradients (not speaking of singularities) are resolved by refinement anyway. One major advantage of those Elements is their superconvergent behavior, thus the stress Int…
  • A note regarding Roshaz, John Horspool, owner and sole developer of Roshaz passed away in 2011. R.I.P John ...so sadly this project can be regarded discontinued. regards.
  • Hi Chris, please check if the library is available. Otherwise try the GE binary (which relies on extanal libraries) or the one I compiled (no external libraries required). The missing library should reside in the same folder as the ccx exe-file. …
  • I tested this approach some time ago as a customer followed the rule to accept hexaedral meshes only. Make sure the tets are in in good shape. For reference: http://onlinelibrary.wiley.com/doi/10.1002/cnm.485/abstract
  • the latter one is the reason why I've built ccx statically. Sergio, 9.9E99, 9.9E-99 ... you are pushing the limits infty vs. zero
  • I did not try it so far, but I expect them to differ in the same way as my binaries.
  • Hi Sergio, https://github.com/GeneralElectric/CalculiX/blob/master/releases/CalculiX-GE-OSS-2.10-win-x64.zip unzip --> bin folder (ccx.exe and ccx_MT.exe as well as several dlls you might copy/move together with the exe-files) regards
  • Great news, thanks a lot and have a nice Sunday ... regards ...
  • Victor, thanks a lot! Great work again.
  • Victor, thanks for your compliments, you are welcome, finding workarounds is my daily job I really like mecway and I'm glad to help a little to improve the users experience. I'm really looking forward to mecway 5 ... regards
Default Avatar

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!