Skip to content

Releases: JuliaFEM/FEMBase.jl

v0.3.0

27 Nov 22:07
Compare
Choose a tag to compare

v0.3.0 (2019-11-21)

Diff since v0.2.2

Closed issues:

  • get_integration_points for Seg2 not working anymore (#52)

Merged pull requests:

v0.3.1

22 Dec 13:07
v0.3.1
Compare
Choose a tag to compare

v0.3.1 (2019-12-13)

Diff since v0.3.0

Closed issues:

  • TimerOutputs (#68)
  • ERROR: LoadError: LoadError: invalid subtyping in definition of Poi1 (#67)
  • ERROR: LoadError: ArgumentError: Package FEMBasis does not have Tensors in its dependencies: (#66)

v0.2.2: Minor changes to there and here

08 Apr 15:29
02637af
Compare
Choose a tag to compare
  • Prefix with package name for foreign names (@KristofferC)
  • Use Appveyor to test package in Windows machines (@TeroFrondelius)
  • Fix LaTeX equation representations in documentation (@rezarastak)
  • Do not test for Julia v0.7 anymore (@ahojukka5)
  • Losen type definitions to make FEMBase work with 32-bit architecture (@ahojukka5)
  • Update documentation deployment script (@ahojukka5)
  • Update add! so that dofs can be given with abstract vectors or tuples (@ahojukka5)

v0.2.1: Small changes in api (#34)

01 Sep 19:16
d96a0d3
Compare
Choose a tag to compare
* New function get_problem(problem, name) to fetch a problem from a
  analysis.
* Update docstrings.
* Connectivity can be given with tuple when creating new element.
* Be more information (@info) when calling functions to be more
  responsible.
* Preparations to separate topology and basis.
* Remove function to update properties with string pairs, it's quite
  unpractical approach (we still should implement something like
  update_properties!(...) ).
* `add_elements!`, `add_problems!`, takes also varargs, so can also call
  `add_elements!(p, e1, e2)` instead of creating first iterable.
* `update!` can take list of elements as tuple.
* `SparseMatrixCOO` and `SparseVectorCOO` can be converted to full
  matrices / vectors using `Matrix` and `Vector`.
* Comparison of `SparseMatrixCOO` with matrix / vector using `isapprox`.
* `add!` returns nothing.

v0.2.0

21 Aug 17:43
5201c70
Compare
Choose a tag to compare
Make package compatible with Julia v1.0 (#33)

v0.1.9

05 Jul 08:20
Compare
Choose a tag to compare
Fix deprecations (#27)

v0.1.8: New public function write_results! (#26)

03 Jul 15:26
44b89bd
Compare
Choose a tag to compare
`write_results!(analysis, writer)` is a function which is used to implement new results writers for some analysis. Usage example in pseudo-level:

```julia
type XdmfWriter <: AbstractResultsWriter
    # stuff
end

type Dynamics <: AbstractAnalysis
    # stuff
end

function FEMBase.write_results!(analysis::Dynamics, writer::XdmfWriter)
    # fid = open(writer.filename)
    # for problem in get_problems(analysis)
    #     field = problem("displacement", analysis.time)
    #     write(fid, field)
    # end
    return nothing!
end
```

v0.1.7

25 May 15:02
1b4027f
Compare
Choose a tag to compare
Fix time interpolation (#23)

v0.1.6: Add new functionality to help testing of packages (#22)

17 May 14:25
f77832e
Compare
Choose a tag to compare
- Implemented macro @test_resource(name), which returns full path to the
  test resource (=file), according to the rule that resources of test
  are under `test` directory and subdirectory, which matches to the name
  of the test file.
- Implemented functions `read_mtx_from_file` and `read_mtx_from_string`,
  which can be used to read matrix files exported by ABAQUS, when using
  commands
  ```ABAQUS
  *MATRIX GENERATE, STIFFNESS, MASS, LOAD
  *MATRIX OUTPUT, STIFFNESS, MASS, LOAD
  ```

v0.1.5: Add new public functions (#21)

16 May 05:52
850c8eb
Compare
Choose a tag to compare
- add_master_elements!, add_slave_elements!, get_master_elements,
  get_slave_elements to work with elements in contact problems.
- eliminate_boundary_conditions! to eliminate boundary conditions