Time-varying rates of multilayer wells - *.pow file

Hey Feflow-community,

I am trying to build my first transient model out of my steady state model. But I become desperate with the assignment of multilayer wells with changing pumping rates over the years.
I´ve got around 300 wells, which have different pumping rates in each time period (3 periods).
I understood from another topic in this forum, that I need two files:

one with the wells (X,Y,screentop/bottom, etc.) and the time-series ID.
example:
Feflow_well TS-ID X Y Z screentop screenbot
1 1 737676.921 2515302.032 2234 2214 2034
1 2 737676.921 2515302.032 2234 2214 2034
1 3 737676.921 2515302.032 2234 2214 2034
2 4 734922.1703 2509961.021 2197 2177 1997
2 5 734922.1703 2509961.021 2197 2177 1997
2 6 734922.1703 2509961.021 2197 2177 1997
3 7 734272.1437 2515803.173 2210 2190 2010
3 8 734272.1437 2515803.173 2210 2190 2010
3 9 734272.1437 2515803.173 2210 2190 2010

Thus, each well has three TS-ID is that right????

And the second file is a .pow file containing the TS-ID and the pumping rate value.
example:
TS-ID Rate
1 1218.982192
2 1225.928585
3 1232.876712
4 975.1857534
5 980.7428681
6 986.3013699
7 975.1857534
8 980.7428681

As I get an error message something is wrong with the files.
Could someone explain me, how the pow-files look like and how I do the assignment?

Thank you in advance!
Lisa

Considering the number of wells you want to integrate in your model I suggest to make a [b]Parameter Link[/b]. The introductory tutorial shows the workflow how to assign Multilayer Wells (pages 36+37):

www.mikepoweredbydhi.com/-/media/shared%20content/mike%20by%20dhi/flyers%20and%20pdf/product-documentation/feflow-introductory-tutorial.pdf

This video may also help with the assignment. https://www.youtube.com/watch?v=Gsf6zmqY7XU

A format description about the pow-file format can be found in the FEFLOW Help. For simplicity I copy and paste the important part from the FEFLOW Help.

The text of the first comment line beginning with a '!' character is interpreted as the name of the time series (first character is skipped and 12 characters are significant).

One or multiple time series can be contained in a single file. The ID number for the functions is mandatory when having more than one series in a file, but can be skipped in case of only one series. The ID is defined by a leading line beginning with a '#' character. The syntax is:

[font=courier]# ID1
! Comment line for time series 1
! ...
x1 y1
x2 y2
...
xm ym
END
# ID2
! Comment line for time series 2
! ...
x1 y1
x2 y2
...
xn yn
END
# IDn
! Comment line for time series n
! ...
x1 y1
x2 y2
...
xo yo
END
END
[/font]

A double END statement is required at the end of the file to both end the definition of the last time series and the file.

[b]Time-series Properties[/b]

The *.pow file can also contain curve-type, time-mode, time unit, unit class and user unit properties in the comment lines that are considered at import. The properties are written in square brackets, and multiple options are separated by a semicolon:

[font=courier]
# 1
!
x1 y1
x2 y2
...
xn yn
END
# 2
!
! [type=Polylined;option=linear;timeunit=s;unitclass=LENGTH;userunit=m]
x1 y1
x2 y2
...
xo yo
END
# 3
!
! [type=Constant;option=cyclic;timeunit=d;unitclass=TEMPERATURE;userunit=^0C]
x1 y1
x2 y2
...
xp yp
END
END
[/font]

[b]Gaps[/b]

Gaps in time series are identified by the keyword GAP, as illustrated in the below example. The gap extends from the time in the value pair before the gap to the time in the value pair after the gap.

[font=courier]
# 2
! Example for gaps
0 0
0.5 1
1 0.7
GAP
10 15
100 10
END
END
[/font]

Hey Björn,
thank you for your answer.

I managed to create the .pow file by checking out the tutorial project in Feflow.
The format description is not so easy to understand without example...

Kind regards
Lisa

Great to hear that you managed to create a pow-file. If you need an example you may always create a "test" pow-file. Use the Time-Series Editor and generate an artificial time-series. After that, you can export the file. Load the file into an ASCII based editor and try to understand the file format.