Activity for swordfishtrombone
-
swordfishtrombone committed [r320]
merged g3_logger branch into trunk
-
fix to get working with later model file (no count)
-
Switch to petsc based solver for Zv2 example
-
elmap/materials correction for config file
-
Added CreatePetScScript routine back in for Viking
-
sample job script for viking (7)
-
sample job script for viking (6)
-
sample job script for viking (5)
-
sample job script for viking (4)
-
sample job script for viking (3)
-
sample job script for viking - switch to unix line endings
-
sample job script for viking - ready for testing
-
sample job script for viking
-
updates to makefiles after building on viking (York)
-
updates to makefiles after building on viking (York)
-
Added makefile for simple in-folder nodal strain build, to mirror those already in itkReader (convertVoxfeScript) and remodelGraph (forgot to add)
-
Added makefile for simple in-folder nodal strain build, to mirror those already in itkReader (convertVoxfeScript) and remodelGraph
-
prototype cmake recipe for remodeller
-
Hi Alex, I haven't been able to reproduce the problem, but there may well be an issue.... can I just clarify where you're saving the constraints file? (Saving a backup constraints file might always be a good idea.) There's always been an issue between the state file and the constraints output because the constraints are not sufficiently well defined. In short, it's a bug in the original file format - the constraints should have a group number so that eg. forces can be correctly distributed over them....
-
added logging & voxel size check to ReadVoxFEScript
-
fixes to several errors introduced during log additions
-
updates to jam files (and some doc) to install to a sub-directory
-
adding boost jam build/remodelControl for hymc; building -- needs testing
-
adding boost jam build for hymc
-
log tweaks
-
added glob num to output
-
added pt dump in strain processing
-
dumping glob node/displ for petsc read for all subclasses
-
dumping glob node/displ for petsc read
-
clean up/ logging commands
-
more logging commands
-
logging commands
-
reworking displ table to track strain attr error on old models (3); building
-
reworking displ table to track strain attr error on old models (2)
-
reworking displ table to track strain attr error on old models
-
#include <iterator> for std::inserter
-
Tweaks to build on windows: i) static version of g3log ii) boost allowed from 1.65 iii) snprintf define forbidden with msvc 2017
-
replaced using std.
-
replaced using std. Also further output to log file from readers
-
adding VOXFE_LOG to strain output
-
moved things around to add g3log directly into the source; only tested on ubuntu
-
dumping nodes
-
log calls
-
added nicer defines/guards
-
working logger into itkReader
-
After rejigging c++14 flags, got build with g3 logger
-
switched to tabs only to ape format
-
moved v0 script to shell
-
Convert from 'ParaBMU' displacement output to early 'v0' solver output to import into old (Borland) VoxFE gui
-
added file write test class
-
removing boost::log trial, adding g3log. boost doesn't like to load as a plugin. g3 adds a simple(ish) library with crash dump ability (least that's the hope)
-
Working logger; writes to temp dir
-
Adding boost logger, working into itkreader
-
build on linux PV 5.5.2. Required major change to CMakeLists. Also vtkFloatArray->GetTupleValue etc to vtkFloatArray->GetTuple [Plugin 1.1]
-
add logging tool
-
const tweak
-
output only selected (extracted) blocks to script
-
tweak -- truncation of YM & PR fixed
-
tweak -- broken quote mark
-
tweak on displ name, consistent for output, still with mutiplier
-
modified to work from the named displacement file and has optional param to multiply displ values
-
Hi Felipe, Thanks again for your interest -- a stress module (with von Mises) is long overdue, and although under discussion, is unlikely to happen until later this year... other work has taken me away unfortunately. If I get a clearer idea, I'll let you know, - regards, Richard
-
Vox-FE and ParaView with MS-MPI support
-
Hi Felipe, Thank-you for your interest. The plugin is very specific to particular versions of paraview and has to be built against it from scratch. With regard to paraview, there is some work still ongoing, but it's not full time, and I don't think your idea (of using MPI to load data) has been discussed for some time (parallelising the solver was always of much greater importance). In any case, parallel reading would not help much unless you happen to have access to a large multi-core machine with...
-
Problems with the solver
-
Error at the write out step:
-
Can't find the circ2.script in the tutorial videos
-
testing with CB example
-
Converting assembly routine; got build
-
Converting assembly routine
-
Fixing reading of materials
-
Non-building FE assembly test-code, borrowed from set on ccpforge (which assumed LSMs were separately generated eg. by old solver)
-
Hi, might still be something fairly simple, so can you try: file /home/eduardo/Downloads/VoxFESolver if the file is recognized, try chmod +x /home/eduardo/Downloads/VoxFESolver and try re-running the script (note: you should not need to run as sudo) Richard ps if that still fails run ls -l /home/eduardo/Downloads/VoxFESolver
-
Hi, might still be something fairly simple, so can you try: file /home/eduardo/Downloads/VoxFESolver if the file is recognized, try chmod +x /home/eduardo/Downloads/VoxFESolver and try re-running the script Richard ps if that still fails run ls -l /home/eduardo/Downloads/VoxFESolver
-
Hi Eduardo, it's ok... I think you have Ubuntu 16, so try the VoxFeSolver binary in solver-binaries / v2 / Ubuntu / 16.04_static regards, Richard
-
Hi Eduardo, I put some executable versions of the solver in the solver-binaries directory. They are static versions, which means they don't need all the dependent libraries, but they are quite big. There are also snapshots of the source and the makefiles I used to create them (which you will need to edit if you want to build yourself). Hopefully this should get you started! regards, Richard
-
Hi Eduardo, it looks like you definitely have a build system, but presumably building the solver still fails? The script you have assumes Ubuntu 14 though, but now I know that I can probably update it. I'll try to get back to you tomorrow, regards, Richard
-
Hi Eduardo, it's probably a configuration issue, so quite difficult for me to check. Probably the compiler is still not set up. Did you follow the steps in sections 2.3.1 and 3.1 of the building guide? If so, what happens when you type : g++ regards, Richard
-
Hi Eduardo, it would be easier if you said what the problem was, or even sent me a screenshot. I suspect you haven't installed the compiler or the dependent libraries (such as mpi). Look through the pdf again... basically you need to run through all the things that start with sudo apt-get install <...> regards, Richard
-
Hi Eduardo, Somewhere I had a document giving a blow by blow account of using oracle's virtual box to install ubuntu within Windows. This is probably the easiest thing to try first. I can't seem to find it, but there will be help out there if you just google it. That would be a great start... I'll try to send some more info when I can, regards, Richard On Wed, May 24, 2017 at 3:21 PM, Eduardo Lamb Lautert eduardolautert@users.sf.net wrote: Hi Richard, thank you vary much for the help. We are now...
-
Hi Eduardo, I tracked down the virtual box doc, so i've attached it here - this describes installing the old solver, which you can try, but I wouldn't really recommend. If you can get ubuntu up and running, let me know and I'll try to send some more help files. I'm still using Ubuntu 14.04 at this end, so possibly I could send you binary files (assuming that's what you decide to install too) regards, Richard
-
Hi Eduardo, we've only tested the solver on linux systems; it may be buildable upon windows but you would need to work out all the dependencies and install mpi etc. I have a build script bundle of the solver which may help you, based on Ubuntu installed through Oracle virtual box on windows. I'll try to dig it out tomorrow, - regards, - Richard
-
legacy awk script now outputs to subdir
-
clean up and addition of voxfeNodalStrain to ma...
-
Direct nodal strains; Fix for: i) existence of ...
-
Fix to check if to use strain file
-
Adding direct nodal strains; imported results l...
-
Adding direct nodal strains; building at least
-
Implementing direct strain mapping
-
Added # column check to dipl readers
-
Starting to add direct strain reading on nodes
-
Outputting 10-comp nodal strains; seems ok, but...
-
Added output of metis global node file as optio...
-
... and I've added the missing file back in too! Richard
-
Hi, if you load beam.voxfe file (and change the file range to 1 -- 320), you will...
-
Hi Jonathan, I've added a zip of tutorial files on the main site. The circ example...
-
Implemented simple nodal strain calc using a gl...
-
output of node0 values in element sequence so c...
-
remoworking the nodal strain calc -- not sure i...
-
working in missing nodes from output file - pro...
1 >
