Dear Praveen, Sorry, that error message is not very good. Try using backGround(1,0)=subSonicOutflow mixedDerivative(1.*t+1.*t.n=300.) as in cg/cns/cmd/cicSubSonic.cmd Regards, Bill Praveen C wrote:
HelloI am trying to run inviscid, compressible flow over an airfoil. I used naca0012.cmd from overture for the grid. But I get an error in boundary conditions. My cmd file and the error is below. Can somebody point out what I am doing wrong ?Thanks praveen * * cgins: command file for flow past a naca0012 airfoil * use either naca0012.hdf or naca.hype.hdf * * naca.hype$tFinal=10.; $tPlot=1.; $debug=3; $grid="naca0012.hdf";* $grid * compressible Navier Stokes (Jameson) exit * show file options open naca.show exitturn off twilight zone *final time $tFinal. times to plot $tPlot debug $debug plot and always wait * no plotting pde parameters * the next value for nu is too small to have any effect. mu 0. kThermal 0. rate constant 0. done cfl .75 boundary conditions all=slipWall backGround(0,0)=subSonicInflow, uniform(r=1.0,u=1.0,v=0.0,e=10.0) backGround(1,0)=subSonicOutflow backGround(0,1)=slipWall backGround(1,1)=slipWall done initial conditions uniform flow r=1.0,u=1.0,v=0.0,e=10.0 done continue $$$$$$$$$$$$$$$$error$$$$$$$$$$$$ grid name side axis boundary condition and name ---- ---- ---- ---- --------------------------- 0: backGround 0 0 8 : subSonicInflow 0: backGround 1 0 10 : subSonicOutflow 0: backGround 0 1 4 : slipWall 0: backGround 1 1 4 : slipWall 1: airfoil-grid 0 0 -1 : periodic 1: airfoil-grid 1 0 -1 : periodic 1: airfoil-grid 0 1 4 : slipWall 1: airfoil-grid 1 1 0 : none ****************************************************************** initialize the solution... Parameters::updateTurbulenceModels: turbulenceModel=0interpolateAndApplyBoundaryConditions (start) steps=-1 t=0: number of array ID's has increased to 543 MappedGridOperators::applyBoundaryCondition:mixed BC:ERROR: a(1)==0 MappedGridOperators::applyBoundaryCondition:mixed BC:ERROR: a(1)==0 Overture::abort: I am now going to purposely abort so that you can get a traceback from a debuggerAbort trap