bb5db3e79c
structured according to family
2021-08-04 16:17:29 +02:00
e95157f039
unified behavior
...
extra dimensions (here: slip systems) are added to the left, inline with
.equivalent and .related
2021-07-25 20:32:24 +02:00
d1c3d767cc
documenting
2021-07-25 19:59:26 +02:00
de428efca5
add_pole is working again
2021-07-18 18:58:05 +02:00
19ca99e033
matching name
2021-07-18 16:39:52 +02:00
2217c3d143
unified help
2021-07-18 15:42:36 +02:00
2826e61ea1
no need to split code over two files
2021-07-13 07:09:19 +02:00
92ca010b7c
Philip's corrections
2021-07-04 23:25:00 +02:00
5202da13ea
better not have a "Lattice" object with "lattice" parameter
2021-06-07 21:49:04 +02:00
41e5f0c06c
re-introduced multiple inheritance
2021-06-06 22:25:42 +02:00
0722f4f754
disable if not possible
2021-06-03 11:22:28 +02:00
3c8d06b6f1
encapsulating all lattice(-family) related data
2021-06-03 11:18:00 +02:00
4701eea10f
decoupling Orientation and Lattice/LatticeFamily
2021-06-03 10:02:49 +02:00
03d3f362e6
equality checks
...
note: doing this type of comparison means:
- LatticeFamily('cubic') == Lattice('cF')
- Lattice('cF') != LatticeFamily('cubic')
we have the same behavior for comparison between Orientation and
Rotation
2021-06-03 09:38:43 +02:00
3b150ddbea
simplified/separated
2021-06-03 09:22:54 +02:00
87e94b6cf4
sorting
...
most functions require only lattice family, functions that require full
lattice details are at the end
2021-06-03 08:43:56 +02:00
302da1f76a
separating functionality
2021-06-02 17:11:37 +02:00
b55d51491d
separating functionality
2021-06-02 08:48:45 +02:00
e281d8384f
distinguish 'family' and 'lattice'
...
this requires the user to specify a keyword ('*' notation in __init__).
Since all 'from_xxx' methods anyway require a keyword, it does not
causes much more work (one explicit keyword in case of cube orientation
when using __init__ directly).
2021-06-01 21:51:28 +02:00
684016f3e3
utility function without connection to an object
2021-06-01 21:29:35 +02:00
89fc2f05cf
no need to attach static data
...
if needed, a 'kinematics' function that provides slip direction and
plane normal rotated according to the orientation would be helpful
2021-05-27 20:23:22 +02:00
bfc3fe410f
no direct connection to Orientation object
2021-05-27 19:10:23 +02:00
f7e1aad147
single source of truth
2021-05-27 18:44:20 +02:00
545a085c93
no need to hide, just add suffix to avoid clash with string argument
2021-05-27 18:41:42 +02:00
bc8a03b392
Merge branch 'python-polishing' into lattice-into-orientation
2021-05-07 22:04:25 +02:00
9c9286a4be
no connection to the class
2021-05-07 21:51:11 +02:00
cb8dbf6eda
simplified
2021-05-07 21:33:48 +02:00
b1ad8197f2
object oriented approach
...
Orientation (of special lattice) should not have generic attributes
Also, import at the beginning of the file
2021-04-29 20:59:54 +02:00
3977e230b3
documenting and ensuring consistent argument names
...
'name' for a dataset matches the analogy to a file name
2021-04-24 14:47:45 +02:00
44331c504b
__class__ is unknown (says prospector)
2021-04-10 08:29:42 +02:00
bc1454970c
mandatory symmetry
...
if symmetry is not of interest, damask.Rotation should be used
2021-04-06 22:49:08 +02:00
d5806075d4
distinguish isclose/allclose and __eq__
2021-04-05 22:15:03 +02:00
be9e00347b
cleaning
...
dropped support for legacy table
2021-03-27 10:11:31 +01:00
fc172921fb
unified citation style continued
2021-03-19 10:41:47 +01:00
002cfbd085
Merge branch 'account-for-floating-point-precision-in-orientation' into 'development'
...
ensures that at least one orientation in the FZ is found
See merge request damask/DAMASK!337
2021-02-15 20:53:37 +00:00
89e8ca4535
renamed and shortened _separate_arguments()
2021-02-15 11:22:42 -05:00
fe63adcca4
mimic python error message and ensure that error is raised
2021-02-12 18:20:39 +01:00
f1b8978e21
accept variables that will be used
...
**kwargs allowed the use of extraneous arguments
2021-02-12 11:24:12 +01:00
4bcbcb34d0
ensures that at least one orientation in the FZ is found
2021-02-09 23:58:00 +01:00
2d6e6a2370
Rotation composition uses "*"; application of Rotation to object uses "@"; "apply()" works on both
2021-01-12 18:57:33 -05:00
d8b4b7e0f5
!= and == work componentwise
2021-01-03 21:52:19 +01:00
35ca1ffb0a
consistent copy functionality
2021-01-03 12:03:40 +01:00
5ab2847b36
polishing
2020-11-23 20:06:34 +01:00
c58f9f23a1
read old version while resolving merge conflicts
2020-11-22 14:32:32 +01:00
24fabdec22
Merge branch 'development' into vector-mechanics
2020-11-22 12:02:29 +01:00
a87596cefc
return rotation type (ensures proper rotation)
2020-11-19 22:36:19 +01:00
894a8de9f9
avoid name clash: as_Rodrigues_vector(vector = ...)
2020-11-19 14:31:14 +01:00
564ee6c96a
make uvw/hkl keyword-only arguments
...
avoid to prefer one over the other, since they are mutually exclusive
2020-11-18 16:45:53 +01:00
89c748fdf1
Merge remote-tracking branch 'origin/development' into vector-mechanics
2020-11-18 13:55:05 +01:00
6bedd84759
self-explanatory names
2020-11-18 08:15:04 +01:00
Martin Diehl