sophie liu

The same error "illegal storage access" happened with tool "generate energy wave spectrum" with the version of MIKE 21 I am using. After I installed service pack 3, the problem is gone. But I still got the error with tool "wave generated current and setup". Any ideas? Thanks.

Regards,
Sophie

Hi Ricardo Machado,

There is no sign of ranning out of memory (the MIKE ZERO shell takes up to 17MB (computer memory 16GB)) or hard disk space (at least 1TB is left on D drive). Is there any mistake made in the parameters which may cause the problem? Or could there be a bug in the tool?

Regards,
Sophie

Hi everyone,

I'm working with project "Port" inside the MIKE 21 PMS example. I managed to generate wave radiation stresses from port-2d.pms. I then used this data in tool "wave generated current and setup". Providing parameters for this tool is okay, but there is a illegal storage access error when executing. Does anyone encounter this or have any idea how to fix it?

Regards,
Sophie

Hi Ricardo Machado,

Thanks for reply. A further question is, does the location of the tide gauge matter? For example, in my model, the river downstream flows into the sea, can I use the tide data just at the river mouth? Or a farther location (at sea) should be included?

Regards,
Sophie

Hi,

Just want to know how to include tidal effect in MIKE 21 model, is it to use tide data as boundary conditions?

Regards,
Sophie

Hi, just wondering have you figure out how to include tidal effect in MIKE 21? Also, when you say you activate tidal potential, does it mean use tide station data for boundary conditions?

Regards,
Sophie

Hi Mathieu,

Thanks for reply. I no longer have that problem now.
But I will post another topic to discuss what issue I encountered now.

Regards,
Sophie

Hi everyone,

I am facing a problem using MIKE 21 to simulate river flood.
I use smoothed DEM to represent bathymetry and also dfs0 for initial water surface. I've checked that the initial condition assured the boundary points are wet.
I use flux as the inputs for two inflow boundaries(west) and tide level for one outflow boundary(east), it gives "elevation too low on flooded boundary", which stops at the last point on the eastern outflow boundary.
After I reduce one of the inflows, it gives another error "one point wide open flux boundary". Are these two typical problems when setting up boundary conditions? Are there general reasons why they happen?

Thanks,
Sophie