How to import many multi-layer wells in 3D model?

Hello,

I have the data of 1200 withdrawing points in the study area. For each point I have: X, Y, the top and the bottom, and the pumping rate. I want to import the data as 4th type (well) boundary conditions, but I don't know how to automatically import multi-layer wells and I also don't know how to find which layers these wells belong to.

Please give me some suggestions!

Thanks a lot!

Thuy.

There is currently not automatic import for this kind of data. You'd have to somehow decide on the slice where the bottom of each well is located, and then subdivide your database in one file for each slice, containing the entire pumping rate on the bottom slice and zero values on the upper slices in the elevation range of the well screen.

Thank you very much for your reply!

I'm now trying to do divide wells into layers as the following:
      - To add all wells as points in supermesh, them all of them become points in superelement.
      - To export all slice elevation as file '.trp'
      - To use the tool mix_trp with function "F=F1-F2" in cygwin in order to compare all slice elevation with the top and bottom of wells.

I have many times the error message in cygwin like this "C:\cygwin\bin\sh.exe:  *** heap allocated but not at 0x9C0000    3 [main] sh 7520 sync_with_child 6188 <0xF8> died before initialization with status code 0x1    396 [main] sh 7520 sync_with_child: *** child state waiting for longjmp /usr/bin/mix_trp: Cannot fork: Resourse temporarily unavailable"

Could you please explain it for me? And I still can get the result after doing it again and again without any change in data.

Have a nice weekend!
Thuy.

To be continued ...

After comparing all slice elevation with the bottom and top of well, I got trp files which are wells for each layer and common wells for 2 layers as well. Then I input these data layer by layer (assign database/Inverse distance weighting interpolation-1/Well/F2) and I always have many log messages:
"Well nesting: The generated well node ... could not desired vs. actual position : X:.... Y:..."

Could you please help me to know what happen?

Thank you!
Thuy.