Dear Seeonggyu,
Thank you so much for your reply.
C:\Temp\SM_nwt_test\SWAT-MODFLOW>SWAT-MODFLOW3.exe
SWAT2012
Rev. 636_smrt
Soil & Water Assessment Tool
PC Version
Program reading from file.cio . . . executing
MODFLOW is being used
Using NAME file: modflow.mfn
forrtl: severe (29): file not found, unit 146, file C:\Temp\SM_nwt_test\SWAT-MODFLOW\fort.146
Image PC Routine Line Source
SWAT-MODFLOW3.exe 00007FF6149EF2A4 Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF6149B0E89 Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF6144754F4 Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF614715A11 Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF61471E700 Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF614984F98 Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF614811F77 Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF614A8812E Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF614A88649 Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF614A8856E Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF614A8842E Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF614A886BE Unknown Unknown Unknown
KERNEL32.DLL 00007FFC577D74B4 Unknown Unknown Unknown
ntdll.dll 00007FFC597226A1 Unknown Unknown Unknown
Since my swatmf_log.txt stops before the line, "swatmf_init: MODFLOW files have been read", I suspected that even my NWT version MODFLOW model might still be a source of error. So, I tried building a simple MODFLOW model using the SWAT-MODFLOW gui instead of using my MODFLOW, but I still get the same error.
One thing that might be noteworthy is that my basin is quite big (~45000km2) and my SWAT model is quite complex (~7500 HRUs). MODFLOW is relatively simple but still big in scale (~45000 active cells; 1km2 grid). It took 6-8 hours every time I attempted to build a SWAT-MODFLOW model using my models, as the linking process takes really long.
Thinking that my large/complex SWAT might be causing issues in memory or some kind of input size limit that might exist for SWAT-MODFLOW, I also tested running my SWAT-MODFLOW model (the one with the NWT version MODFLOW; the link to the zip file is provided above) with SWAT-MODFLOW deactivated. I expected my SWAT-MODFLOW model should run fine for the SWAT part only, as my SWAT model alone runs well, but I am still getting the following error. Since it says "access violation", I checked the security under the properties of the project folder, and I do have full access and control of the folder. I have no idea what this access violation means.
C:\Temp\SM_nwt_test\SWAT-MODFLOW>SWAT-MODFLOW3.exe
SWAT2012
Rev. 636_smrt
Soil & Water Assessment Tool
PC Version
Program reading from file.cio . . . executing
Executing year 1
forrtl: severe (157): Program Exception - access violation
Image PC Routine Line Source
SWAT-MODFLOW3.exe 00007FF7371D24F2 Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF737098D24 Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF7370AE974 Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF73700725C Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF737284D36 Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF737111F77 Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF73738812E Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF737388649 Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF73738856E Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF73738842E Unknown Unknown Unknown
SWAT-MODFLOW3.exe 00007FF7373886BE Unknown Unknown Unknown
KERNEL32.DLL 00007FFC577D74B4 Unknown Unknown Unknown
ntdll.dll 00007FFC597226A1 Unknown Unknown Unknown
Regarding the program versions, I am using the latest versions, QGIS (3.22.12) and SWAT-MODFLOW version from your github (2.3.1). I've also checked that the programs run fine by building and running a SWAT-MODFLOW project using the example data from your github, so I doubt I have any issue with the programs.
As much as I am excited about SWAT-MODFLOW, I am so frustrated that I am not able to integrate my SWAT and MODFLOW models, which work fine individually and go through the linking process without any error.
I would greatly appreciate your help on the issue.
Thank you so much, and I look forward to hearing back your thoughts.
Best,
Jy