{"push_id":592094052,"size":44,"distinct_size":1,"ref":"refs/heads/g-bhutani12/multiphase-keps","head":"ba76ec2a5b1b75be63776ae1a6f51f3167da20f2","before":"971bccc0ae70f73753f89fff007d7334499e0b8c","commits":[{"sha":"07016062d2e7d30695190fd6954da0721e161921","author":{"email":"532bde457235e9d64931f5c49524f3b8a5b197c2@imperial.ac.uk","name":"Stephan Kramer"},"message":"Fix make install on archer.\n\nThis fixes make bin/burgers_equation which is a prerequisite for make\ninstall.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/07016062d2e7d30695190fd6954da0721e161921"},{"sha":"9045e06179487ac44cbd9430ab2f32c9384a0734","author":{"email":"0c8cdf8790306ce919b10d0aa080d515b3b1f05b@anu.edu.au","name":"Rhodri Davies"},"message":"Reorder modules and other hacks for intel 14 build.\n\nUsual intel voodoo.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/9045e06179487ac44cbd9430ab2f32c9384a0734"},{"sha":"67717a77d7db176fcb82b0573785289ec02f6ded","author":{"email":"0c8cdf8790306ce919b10d0aa080d515b3b1f05b@anu.edu.au","name":"Rhodri Davies"},"message":"Fixes in gmsh reading with intel.\n\nThis should fix gmsh ascii reading for intel 11 as well (which was\npreviously broken/unsupported).\n\nThis is based on the new understanding (from Ben at NCI, Canberra)\n of the intel bug/feature where it disagrees with gcc about the file positioning. Basically after a\n\n  read(unit, '(I1)', advance='no')\n\n(Note there's nothing actually read since there are no variables on the right) - intel\ndecides that the advance='no' must apply to the next read(), whereas gcc simply applies\nthe default in the next read. Have now moved the intel specific code to directly after\nthe read following a call to ascii_formatting() call (which has the above read statement), instead\nat a random place in the next subroutine along.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/67717a77d7db176fcb82b0573785289ec02f6ded"},{"sha":"02a259567f4b235bf0e5a725aa10f73ba9d52ac0","author":{"email":"0c8cdf8790306ce919b10d0aa080d515b3b1f05b@anu.edu.au","name":"Rhodri Davies"},"message":"Adjust tolerances in a few tests to pass with intel.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/02a259567f4b235bf0e5a725aa10f73ba9d52ac0"},{"sha":"2ac1960cec274337c71cbd6ec204b0476b201d27","author":{"email":"0c8cdf8790306ce919b10d0aa080d515b3b1f05b@anu.edu.au","name":"Rhodri Davies"},"message":"Sort indentation to see if this placates intel.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/2ac1960cec274337c71cbd6ec204b0476b201d27"},{"sha":"9050e252a6795bddde6a63e8be190176722524da","author":{"email":"532bde457235e9d64931f5c49524f3b8a5b197c2@imperial.ac.uk","name":"Stephan Kramer"},"message":"Changes in configure to enable intel 14 build.\n\n* Pass on optimisation flags to CFLAGS and CXXFLAGS. Previously these\n  were only in FCFLAGS to hide bugs in libvtkfortran and libjudy.\n* The bug in libvtkfortran consisted of a non-standard way of using a single char as the\nlast member of a struct to store a longer string by mallocing the struct\nwith the extra bytes needed. There seems a variety of ways to define\nthis last member: 1) char name 2) char name[1] 3) char name[]. 1) is\nwhat was used here but is non-standard. According to various source 2)\nis also non-standard but used in so many places that it \"works in\npractice on all known compilers\". 3) is c99 standard that has not been\nincorporated in c++ standard. 1) proved not to work with -O3 which is\nprobably why we never passed these optimisation flags on. Instead of\nusing these variable length struct hacks, we now simply allocate a\nseparate buffer to store the field name.\n* Switch off aggr. loop optimisations in libjudy.  This is to workaround\nhttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755099 when passing on\noptimisation flags to libjudy.\n* Some other improvements in our fortran wrapper around libjudy (using\n* bind(c)). Not strictly necessary but an improvement nonetheless.\n* Add -ip -Xhost optimisation flags for intel build.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/9050e252a6795bddde6a63e8be190176722524da"},{"sha":"fc8501af0fdda616540e5c21aae05bd204a6b426","author":{"email":"532bde457235e9d64931f5c49524f3b8a5b197c2@imperial.ac.uk","name":"Stephan Kramer"},"message":"Merge branch 'Fluidity-intel-build'\n\nThis allows Fluidity to be build with intel 14. It also fixes gmsh ascii\nreading with older intel versions (only intel 11.1 is currently known to\nwork).","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/fc8501af0fdda616540e5c21aae05bd204a6b426"},{"sha":"86d5afb151eafbacb972421996dd84d613c59014","author":{"email":"532bde457235e9d64931f5c49524f3b8a5b197c2@imperial.ac.uk","name":"Stephan Kramer"},"message":"Only pass -fno-aggressive-loop-optimisation to libjudy when using gcc >= 4.8.\n\nFixes #23. Option didn't exist before 4.8 - so presumably not necessary.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/86d5afb151eafbacb972421996dd84d613c59014"},{"sha":"a00780692080fe534fc8166dce9959c5a9a87a9c","author":{"email":"532bde457235e9d64931f5c49524f3b8a5b197c2@imperial.ac.uk","name":"Stephan Kramer"},"message":"Makefiles changed after intel 14 fixes.\n\nThis is due to \"use module\" reorderings.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/a00780692080fe534fc8166dce9959c5a9a87a9c"},{"sha":"2af7fa7e320d69228e14df4207d995ab0fb988f3","author":{"email":"532bde457235e9d64931f5c49524f3b8a5b197c2@imperial.ac.uk","name":"Stephan Kramer"},"message":"Make fluidity build with petsc master again.\n\nMatGetVecs() has been renamed to MatCreateVecs().","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/2af7fa7e320d69228e14df4207d995ab0fb988f3"},{"sha":"49c16a98ce6a8fe37191b5d226f63211674f8ab2","author":{"email":"0c8cdf8790306ce919b10d0aa080d515b3b1f05b@anu.edu.au","name":"Rhodri Davies"},"message":"Xhost --> xHost.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/49c16a98ce6a8fe37191b5d226f63211674f8ab2"},{"sha":"3c0e7a2ee57777f1aff6fc9ea7749816799af2aa","author":{"email":"0c8cdf8790306ce919b10d0aa080d515b3b1f05b@anu.edu.au","name":"Rhodri Davies"},"message":"Xhost --> xHost in libadaptivity.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/3c0e7a2ee57777f1aff6fc9ea7749816799af2aa"},{"sha":"08381bc788040d6385910b182c7d4d1edd5a872e","author":{"email":"532bde457235e9d64931f5c49524f3b8a5b197c2@imperial.ac.uk","name":"Stephan Kramer"},"message":"Bug-fix in 2+1D adaptivity.\n\nReported by Rebecca. This would show up if using 2+1D adaptivity and\nhaving a python expression for maximum edge lengths but not for\nminimum edge lengths.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/08381bc788040d6385910b182c7d4d1edd5a872e"},{"sha":"dfd8394b2c2f0e43945a58ff947195ad7565b0f9","author":{"email":"bd5b1d4f3151236cda8eedaccad4605a1cce5274@gmail.com","name":"Mark Goffin"},"message":"Fix bug local face numbering for hexes.\n\nModify routine face_local_num_int for FAMILY_CUBE elements so it uses the local node numbers rather than the vertex indices. When\nsetting up the face_lno in add_faces, the functions are passed the vertex indices for the face rather than the vertex node numbers.\n\nPreviously the local face node numbering was incorrect for hex elements, where for some elements (not all) face_local_nodes\ncould return the same local nodes for two different faces. This could and most probably will cause any calculation using hexes and\nface information (e.g. DG) to fail.\n\nAdded unit test for the function face_local_num for linear hex.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/dfd8394b2c2f0e43945a58ff947195ad7565b0f9"},{"sha":"20e5193a316057cbe4850412c3d865c3a6006c3c","author":{"email":"bd5b1d4f3151236cda8eedaccad4605a1cce5274@gmail.com","name":"Mark Goffin"},"message":"Add code to copy element halos to ensure vtkGhostLevels are output if dg-ifying a continuous mesh in vtk_write_fields.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/20e5193a316057cbe4850412c3d865c3a6006c3c"},{"sha":"9620b40a23b9d61b0344391d496caa684865bb75","author":{"email":"2e09d7eb50af03f9521591fa9eebab857bdd65f3@gmail.com","name":"Steven Dargaville"},"message":"Changed schema to allow diagnostic field for the FieldWeightedPartitionValues in the Zoltan options.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/9620b40a23b9d61b0344391d496caa684865bb75"},{"sha":"deb8f744cd0dca230b8a755a57b4954aa419ba02","author":{"email":"532bde457235e9d64931f5c49524f3b8a5b197c2@imperial.ac.uk","name":"Stephan Kramer"},"message":"Bug-fix:  work around for a bug in petsc that pops up with intel 15.\n\nVecGetValues fails a check when passing it a zero-length array. This is fixed in petsc master 18ae1927.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/deb8f744cd0dca230b8a755a57b4954aa419ba02"},{"sha":"5823c4193b2a11b14183505e1ad2109ee74a52ce","author":{"email":"f57514f958a5f99ee15b2033be3aea9edee0bada@imperial.ac.uk","name":"Frank Milthaler"},"message":"adding python tool to convert vtu files to ensight gold files","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/5823c4193b2a11b14183505e1ad2109ee74a52ce"},{"sha":"4e4df7cbf49324ff68a0869052d743d0c1a62e9a","author":{"email":"f57514f958a5f99ee15b2033be3aea9edee0bada@imperial.ac.uk","name":"Frank Milthaler"},"message":"adding description of vtu2ensight to the fluidity manual","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/4e4df7cbf49324ff68a0869052d743d0c1a62e9a"},{"sha":"824d9323a226727c5314a1b849f6546f12150f59","author":{"email":"532bde457235e9d64931f5c49524f3b8a5b197c2@imperial.ac.uk","name":"Stephan Kramer"},"message":"Fix for petsc 3.5.2 (and master).\n\nAlso KSPGetOperators has lost its flag argument. This only affects runs with diagnostic monitors or runs that reuse ksp cache.","distinct":false,"url":"https://api.github.com/repos/FluidityProject/fluidity/commits/824d9323a226727c5314a1b849f6546f12150f59"}]}