>Do I need to change the adjustment factors or should I just let it be?
I would not change any of the adjustment factors until you have reason to.
And how do I import back the calibrated and validated results for visual representation in AGWA? And do these results really need to be calibrated and validated and if yes would SWAT CUP work?
Once you have a successful simulation complete, the AGWA Results form will recognize the simulations and make them available for you to import. If you manipulate the input files outside of AGWA and rerun the simulation, the AGWA results form will recognize the results need to be reimported/updated.
Simulation results are not calibrated or validated in AGWA. AGWA is designed to facilitate the creation of the model input files that can then be used in a separate calibration/validation exercise with external software, or alternatively to view results through the lens of relative change between scenarios/simulations or between subbasins within your watershed. You would need to locate an older version (4.3) of SWAT CUP if you want to use it with the SWAT 2005 in AGWA. We're several SWAT releases behind what the current version of what SWAT CUP supports. Other than SWAT CUP, there are also model independent calibration/validation tools like PEST, or your own scripting in Python, MatLab, or R that is supported. However, given your short timeline, I don't know that you have time to set up calibration and validation, which requires a lot of observed data you may not have yet.
>What does this error mean?>And how do I resolve it?
From the name of the routine and source, it is likely a curve number issue, which would point back to a land cover parameterization issue. In ArcMap, if you add the ..._p_parLUT located in your delineation geodatabase to the map and open it, you'll see the parameters that are used to create the SWAT input files. Each row references a parameterization and a subbasin and has some of the parameters for that subbasin. There should be zero null values; if there are there was a problem with the parameterization. If it's the CN and Cover fields that have null values, it's probably because the CLASS field of the land cover look-up table doesn't have the pixel values in the land cover raster. To fix this, double-check that the land cover look-up table is populated properly. The curve numbers will be in the A, B, C, and D fields, and the CLASS field must be populated with the pixel values of the land cover raster.
Shea