X-Git-Url: http://git.salome-platform.org/gitweb/?a=blobdiff_plain;f=src%2FSMESHGUI%2FSMESH_msg_en.ts;h=32fb70b88b8f712f5f78be845bc2c94a35b623c2;hb=8f903d5ee57f0e646cf05d68d85418c68d497053;hp=fde42d2f404b8363f10c85844cb1db000bc35390;hpb=8731eed9296c2b3541e18b9133971d579d55d9b2;p=modules%2Fsmesh.git diff --git a/src/SMESHGUI/SMESH_msg_en.ts b/src/SMESHGUI/SMESH_msg_en.ts index fde42d2f4..32fb70b88 100644 --- a/src/SMESHGUI/SMESH_msg_en.ts +++ b/src/SMESHGUI/SMESH_msg_en.ts @@ -340,34 +340,6 @@ MEN_CONSTRUCT_GROUP Construct Group - - MEN_REF_ALL - Uniform refinement - - - MEN_REF_HOMARD - Adaptation with HOMARD - - - MEN_HOMARD_CREATE_CASE - New case for adaptation with HOMARD - - - MEN_HOMARD_FOLLOW_ITERATION - Existing case - - - MEN_HOMARD_NEW_ITERATION - New iteration - - - MEN_HOMARD_COMPUTE - Compute - - - MEN_HOMARD_COMPUTE_PUBLISH - Compute and publish - MEN_MG_ADAPT Remesh with MG_Adapt @@ -396,7 +368,7 @@ Publish_MG_ADAPT Publish - + SIZE_MAP_FIELD Size map field @@ -424,10 +396,6 @@ MG_ADAPT_MED_FILE_5 No field in this MED file. - - MG_ADAPT_MED_FILE_6 - The field(s) in this MED file cannot be read. - MG_ADAPT_ERROR Error @@ -458,7 +426,7 @@ LOCAL_MG_ADAPT - local + Local BACKGRND_MG_ADAPT @@ -478,12 +446,20 @@ SIZE_MAP_DEF - size map definition + Size map definition ADVOP Advanced Options + + MG_ADAPT_DIAG_1 + Adaptation succeeded. + + + MG_ADAPT_DIAG_2 + Adaptation failed. + MEN_CONV_TO_QUAD Convert to/from quadratic @@ -3057,38 +3033,6 @@ Check algorithm documentation for supported geometry ADAPT_PREF_NONE None - - ADAPT_PREF_HOMARD_PUBLICATION - Publication of meshes with HOMARD - - - ADAPT_PREF_HOMARD_PUBLICATION_MAILLAGE_IN - IN mesh - - - ADAPT_PREF_HOMARD_PUBLICATION_MAILLAGE_OUT - OUT mesh - - - ADAPT_PREF_HOMARD_YACS - A YACS schema with HOMARD - - - ADAPT_PREF_HOMARD_YACS_MAX_ITER - Maximal number of iterations - - - ADAPT_PREF_HOMARD_YACS_MAX_NODE - Maximal number of nodes - - - ADAPT_PREF_HOMARD_YACS_MAX_ELEM - Maximal number of elements - - - ADAPT_PREF_HOMARD_YACS_TYPE_CONVERGENCE - Test type for a YACS schema with HOMARD - ADAPT_PREF_MG_ADAPT Adaptation with MG-Adapt @@ -3137,37 +3081,13 @@ Check algorithm documentation for supported geometry ADAPT_PREF_MG_ADAPT_SIZE_MAP_BACKGROUND Background - - ADAPT_PREF_MG_ADAPT_MED_SIZE_MAP_BACKGROUND - MED file background size map - - - ADAPT_PREF_MG_ADAPT_TIME_STEP - Time step - - - ADAPT_PREF_MG_ADAPT_NO_TIME_STEP - No time step - ADAPT_PREF_MG_ADAPT_TIME_STEP_LAST Last - ADAPT_PREF_MG_ADAPT_AR - Arguments - - - ADAPT_PREF_MG_ADAPT_ADVOP - Advanced Options - - - ADAPT_PREF_MG_ADAPT_TIME_LAST_STEP - Last time step - - - ADAPT_PREF_MG_ADAPT_TIME_C_STEP - Chosen time step + ADAPT_PREF_MG_ADAPT_TIME_STEP + Choosen time step ADAPT_PREF_MG_ADAPT_TIME_STEP_C @@ -3177,6 +3097,10 @@ Check algorithm documentation for supported geometry MG_ADAPT_SELECT_FILE_0 MG-ADAPT select file + + ADAPT_PREF_MG_ADAPT_ADVOP + Advanced Options + SMESH_VISU_PROBLEM Mesh visualization failed @@ -3392,38 +3316,6 @@ Use Display Entity menu command to show them. STB_CONSTRUCT_GROUP Construct Group - - STB_REF_ALL - Uniform refinement - - - STB_REF_HOMARD - Refinement with HOMARD - - - STB_HOMARD_CREATE_CASE - Creation of a new case for adaptation with HOMARD - - - STB_HOMARD_FOLLOW_ITERATION - Creation of a new case: pursuit of a stored iteration - - - STB_HOMARD_NEW_ITERATION - Creation of a next iteration - - - STB_HOMARD_COMPUTE - Compute the refinement - - - STB_HOMARD_COMPUTE_PUBLISH - Compute the refinement and publish the final mesh - - - STB_EDIT - Edit - STB_MG_ADAPT Remesh with MG_Adapt @@ -4132,30 +4024,6 @@ Use Display Entity menu command to show them. TOP_CONSTRUCT_GROUP Construct Group - - TOP_REF_ALL - Uniform refinement - - - TOP_HOMARD_CREATE_CASE - New case - - - TOP_HOMARD_FOLLOW_ITERATION - Existing case - - - TOP_HOMARD_NEW_ITERATION - New iteration - - - TOP_HOMARD_COMPUTE - Compute - - - TOP_HOMARD_COMPUTE_PUBLISH - Compute and publish - TOP_MG_ADAPT Remesh with MG_Adapt @@ -7060,7 +6928,7 @@ select mesh or sub-mesh and try again CONCURRENT_SUBMESH_APPEARS -The assigned algorithm has the same priority as one assigned to an +The assigned algorithm has the same priority as one assigned to an adjacent sub-mesh, hence it's undefined which algorithm to use for meshing boundary shared by two sub-meshes. Would you like to set the order of sub-mesh computation?