Scribd Logo
Upload

Welcome to Scribd!

  • 506 views

    Swat Run Error

    Uploaded by

    Daniel Twite
    The error is likely caused by file names that are too long for SWAT to read. Shortening the file names so they are 8 characters or less will likely resolve the issue. Another potential cause is corrupt SWAT files. Verifying the file contents and parameters and replacing files from a backup directory can help troubleshoot the problem.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Swat Run Error

    Uploaded by

    Daniel Twite
    506 views3 pages
    The error is likely caused by file names that are too long for SWAT to read. Shortening the file names so they are 8 characters or less will likely resolve the issue. Another potential cause is corrupt SWAT files. Verifying the file contents and parameters and replacing files from a backup directory can help troubleshoot the problem.

    Original Description:

    swat run error

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The error is likely caused by file names that are too long for SWAT to read. Shortening the file names so they are 8 characters or less will likely resolve the issue. Another potential cause is corrupt SWAT files. Verifying the file contents and parameters and replacing files from a backup directory can help troubleshoot the problem.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    506 views3 pages

    Swat Run Error

    Uploaded by

    Daniel Twite
    The error is likely caused by file names that are too long for SWAT to read. Shortening the file names so they are 8 characters or less will likely resolve the issue. Another potential cause is corrupt SWAT files. Verifying the file contents and parameters and replacing files from a backup directory can help troubleshoot the problem.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 3
    At a glance
    Powered by AI
    The key takeaways are to ensure point source data starts and ends within the dates of precipitation data, and to check for incomplete copying of files by SWAT which could result in half copied data.

    The user is having trouble getting their SWAT model to run when importing a point source database file. The file saves but the program crashes on run with an end-of-file error.

    Blank files were being generated because some of the user's file names were longer than 8 characters, which was causing SWAT to fail to read them properly in the executable.

    Question 1

    Can anyone help me with an error in


    ArcSWAT model?
    Hi ,

    I have some trouble getting in my SWAT model to run when I try importing a point source Database file. SWAT will
    save the file, but crashes when I try to run the program. I g0t the error

    forrt1: severe <24>: end-of-file during read, unit 556, file c:\Users\Scenarios\Default\TxtInOut\11p.dat.

    I've made sure the file covers the same range of dates that the weather data has. Any ideas on what is going on? I
    attached one of my 31 point source file to see. The point in my model are refer to water abstractions from river.

    Thanks,

    Answer 1
    Make sure your point source data starts when the precipitation starts and ends when precipitation
    ends. This will help I guess.

    Question 2

    Hi ,

    I have some trouble getting in my SWAT model to run when I try importing a point source Database file.
    SWAT will save the file, but crashes when I try to run the program. I g0t the error

    forrt1: severe <24>: end-of-file during read, unit 556, file c:\Users\Scenarios\Default\TxtInOut\11p.dat.

    I've made sure the file covers the same range of dates that the weather data has. Any ideas on what is
    going on? I attached one of my 31 point source file to see. The point in my model are refer to water
    abstractions from river.

    Thanks,

    Answer 1
    Hello,
    when u get an error forrtl:severe24. Mostly it is incomplete copying of file by SWAT.
    firstly,use 64bit,debug to get the line and source of the error
    Try and check your TXINOUT file and locate the exact file. check the data content of the file. You will see
    that it is incomplete data.
    For my own case, my weather data in subbasin 1 was not copied well (half copied). i checked end of the
    line , i realized it was half copied.
    i had to copy it manually by myself inside the TXINOUT FILE, and i run the model again.
    so it runs. that is how i solved my problem of forrl:severe 24 of wgn (weather data).
    Hope this will work for you too.

    Question 3
    Hi everyone,

    Now this one really does have me stumped (see attached jpeg). I understand that it is a problem with my
    solar file but the one mentioned here 'slr.slr' is completely blank while the other one in the txtinout folder
    (slr1.slr) appears to be ok. I suppose one of my first questions other than what went wrong is why are
    there two slr files in my txtinout folder?

    I was using the ArcSWAT interface to run this simulation.

    Any opinions would be welcome.

    Answer 1

    Ok, quick update. So I went into the txtinout folder and deleted the blank slr.slr file and renamed the
    slr1.slr file to simply slr.slr. This worked, but when SWAT reached my .hmd file it did the same again-
    created a blank hmd.hmd and a populated hmd1.hmd. I could probably get this to work by following the
    same logic as the slr file but I would rather just figure out what the underlying cause is..

    Ok, so this error was caused by a few of my file names having longer than 8 characters. The .pcp files etc
    will read in on the write weather stations but fail in the .exe with this error.

    Question

    My SWAT Model is not run successful it showing the following error, th efile i am attaching with this mail.
    acc to my knowing t
    he error in File.cio

    Answer
    Hello Sanjeet,

    Maybe you can verify the length of the name of your data file in fig.fig. I had this error too when the data
    file's name is too long and SWAT can't read it.

    Good luck

    ERROR (65)
    Answer from Abbaspour
    This is a swat error. It means either there are some strange parameters in your swat files, or some swat
    files are corrupt. Do:
    - make sure swat runs, without swatcup. Just run swat.exe in your main swatcup directory. If it doesn't,
    make sure your swat project is compatible with the swat.exe version in swatcup
    - if swat runs, copy everything from Backup into your main swatcup directory, check that parameters in
    par_inf make sense and run swatcup again.

    Copy your swat in to the swatcup directory...

    You might also like