-
Hi, I'm trying to make JUDI work with custom data types. I prepared the same objects (structs) called Basically all my modifications are located in Now I'm trying to run the modeling_basic_2D.l example. Also is it possible to disable distributed? It makes harder to debug the code P.S.: I'm trying to implement this as JUDI works only with XY axes aligned models, seismic data and the model should be in the same length units and in the same coordinate reference system. I hope I could extend this with h5geo |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 13 replies
-
So it will depend on the operator. For the standard You will also need to make sure it is then converted into an Array in Your addition look quite nice!! |
Beta Was this translation helpful? Give feedback.
-
@mloubout I'm back It seems I prepared To install it one should have C++ compiler supportind 17 standard available. All dependencies will be stored in Now I think I'm going to start preparing Julia project that integrates |
Beta Was this translation helpful? Give feedback.
-
@mloubout I'm still about writing data in custom format. What is the problem: mutable struct H5GeometryOOC <: Geometry{Float32}
h5geo::PyCall.PyObject
container::H5SeisCon # I need to write the data in it
key::String
xkey::String
ykey::String
zkey::String
do_coord_transform::Bool
model_origin_x::Number
model_origin_y::Number
model_orientation::Number
end At the time when I convert OOC Geometry to IC Geometry I rotate the coordinates. function save_to_disk(shot::judiVector, srcGeometry::GeometryIC, srcData::Array, options::JUDIOptions, ::Val{true})
function write_shot_record(srcGeometry::GeometryIC, srcData, recGeometry::GeometryIC, recData, options) thus even if I overwrite these functions I'm still unable to get all information needed (model_orientation, container) to correctly write the data. As I can see save_to_disk is called only from time_modeling function Maybe we could change the How do you think? |
Beta Was this translation helpful? Give feedback.
So it will depend on the operator. For the standard
PDEFull
operator, it will fo first throughprocess_input_data
then throughsubsample
. THe second one is probably the one you need to add for your own HDF5 type:https://github.com/kerim371/JUDI.jl/blob/e2bd96816592c8f5ffc7bd096ae4c0c54a63de21/src/TimeModeling/Utils/auxiliaryFunctions.jl#L755
You will also need to make sure it is then converted into an Array in
time_modeling_serial
in a similar way than SeisCon being read from disk.Your addition look quite nice!!