Denim Umeshkumar Anajwala

The REGIO interface still works with the 'Classic' user interface in FEFLOW 6.0, but not in the 'Standard' (new) user interface. It will no longer be there in the 6.1 version. In the future, user-specific interpolation methods can be implemented directly via COM interfaces, but this will probably not be available before version 6.2. 

You can define the number of decimal places by choosing <<Customize or Create New Formats>> from the file type line when exporting. In the Attributes tab of the DataStore Manager that will come up, for each column detailed settings can be done.

[quote author=Peter Schätzl link=topic=808.msg1967#msg1967 date=1275457939]
To me it seems (on a short glance) that you try to register a module for the regionalization IFM interface in FEFLOW. Do you really want to implement a user-specific interpolation method? If not, you should use the "Simulation" interface. I think (but I am not perfectly sure at the moment) that FEFLOW 6.0 no longer support the regionalization interface.
[/quote]
Thank you Peter - I can get the code to work using the SIMULATION interface - Can you confirm that the REGIO interface is no longer an option? It would be good to know for sure. Thanks again.
Malcolm

This export would only export what you have imported before. To export data for all the nodes, choose 'Special', then click on the 'Hydraulic Head' button and use the export functions in the dark red part of the dialog.

There are three reasonable options:
1. You prepare a shape file (*.shp) with the polygons and a column with recharge for each period. Then choose Join - Polygons - Load the file. In the header of the right box in the upcoming dialog ('Parameter Association'), switch to 'time levels', enter your time stages after clicking on the 'Time levels' button, and link the columns from the shape file to the time levels.
2. You prepare a time series (powerfunction) for each polygon and a polygon file (e.g., shape file) with all the zones. In the polygon file, add a column with the corresponding number of the powerfunction. You can then import the data via Join - Polygons - Load the file. Link to the recharge parameter and choose 'Powerfunction ID'. The blue link indicates that you import time-series IDs.
3. Prepare a distribution for one of the time stages as time-constant recharge, then go to T-List and import that distribution for a certain time stage. Repeat the process until you have all the time stages.

SB,

you would need two files for the import:
1. A pow file with all the time series
2. Another file (trp, shp, ...) with the coordinates of the wells and the corresponding time-series (powerfunction) ID.
First import the time-series (powerfunctions). The import of the wells then can be done with Assign - Database - Import powerfunction ID - Well BC - Automatic (FEFLOW 5.4) or by linking the loaded map file (trp, shp, ...) to the well boundary condition and applying the 'Neighborhood Relationship' regionalization.
Please note that in FEFLOW 5.4 you should not have more than one well in the vicinity of the same node. At import, you would get the pumping rate only of the last well imported. In FEFLOW 6.0 using the Neighborhood Relationship, you can choose to sum the pumping rates of all neighboring well onto the closest mesh node.

BR
Peter

To me it seems (on a short glance) that you try to register a module for the regionalization IFM interface in FEFLOW. Do you really want to implement a user-specific interpolation method? If not, you should use the "Simulation" interface. I think (but I am not perfectly sure at the moment) that FEFLOW 6.0 no longer supports the regionalization interface.

Anyone seen these FEFLOW error messages:

On starting debug:
C:\Documents and Settings\username\Application Data\WASY\FEflow\6.0\modules64.ifm,
line 1: Invalid interface name: "REGIO"!

On trying to register IDW_Direct.dll:
C:\FEFLOW_Files\IFM_Projects\IDW_Direct\X64\IDW_Direct.dll: Designed for a different interface (REGIO)!

Where modules.ifm contains:

Module IDW_DIRECT : REGIO
  DisplayName:  "IDW_Direct"
  Revision:      1.0
  RegisterProc:  RegisterModule
  Description:  "Inverse Distance Weighting Interpolation implemented directly as source code"
  SourcePath:    "C:\\FEFLOW_Files\\IFM_Projects\\IDW_Direct\\IDW_Direct.cpp"
  ModulePath:    "C:\\FEFLOW_Files\\IFM_Projects\\IDW_Direct\\X64\\Debug\\IDW_Direct.dll"
  DebugPath:    "C:\\FEFLOW_Files\\IFM_Projects\\IDW_Direct\\X64\\Debug\\IDW_Direct.dll"
  TimeStamp:    1275441062
  CopyrightPath: "C:\\FEFLOW_Files\\IFM_Projects\\IDW_Direct\\IDW_Direct.txt"
  HtmlPath:      "C:\\FEFLOW_Files\\IFM_Projects\\IDW_Direct\\IDW_Direct.htm"
  RegisteredCallbacks: , \
OnStartRegio
End Module  // IDW_DIRECT

Module DEV01 : SIMULATION
  DisplayName:  "Dev01"
  Revision:      1.0
  RegisterProc:  RegisterModule
  Description:  "Code development test"
  SourcePath:    "C:\\FEFLOW_Files\\IFM_Projects\\Dev01\\X64\\Debug\\Dev01.cpp"
  ModulePath:    "C:\\FEFLOW_Files\\IFM_Projects\\Dev01\\X64\\Debug\\Dev01.dll"
  DebugPath:    "C:\\FEFLOW_Files\\IFM_Projects\\Dev01\\X64\\Debug\\Dev01.dll"
  TimeStamp:    1275410854
  CopyrightPath: "Dev01.txt"
  HtmlPath:      "Dev01.htm"
  RegisteredCallbacks: , \
OnEditDocument
End Module  // DEV01

I'm using Visual Studio 2010 to compile C++ code ....any help appreciated.

T-List is for time-varying material properties. Time-varying boundary condition such as abstraction wells are input by creating a time-varying function (or time series in FEFLOW 6.0), and then assigning the function ID to a well boundary condition. You can also refer to the tutorial in the User's Manual (version 5.4) for the exact procedure.

Thanks Peter. I have no immediate needs as of now. I am collecting data to build a business case of using MODFLOW or FEFLOW for one of our clients.