Atom topic feed | site map | contact | login | Protection des données personnelles | Powered by FluxBB | réalisation artaban
You are not logged in.
Pages: 1
Dear Members,
We want to visualize the volumetric heat source, defined by a function, in a thermal analysis. Unfortunately the CREA_CHAMP - IMPR_RESU combo gives error. Consider this example:
volH_F = FORMULE(
NOM_PARA=('Y', ),
VALE='10*Y'
)
volHeatF = AFFE_CHAR_THER_F(
MODELE=model,
SOURCE=_F(
GROUP_MA=('vol', ),
SOUR=volH_F
)
)
vHFi = CREA_CHAMP(
#OPTION='TOUT_INI_ELEM',
AFFE=_F(
NOM_CMP=('SOUR', ),
TOUT='OUI',
#GROUP_MA=('vol', ),
VALE_F=(volH_F, )
),
MODELE=model,
OPERATION='AFFE',
#PROL_ZERO='OUI',
TYPE_CHAM='NOEU_SOUR_F'
)
...
IMPR_RESU(FORMAT='MED',
RESU=(
_F(RESULTAT=resther, TOUT_CHAM='OUI'),
_F(CHAM_GD=vHFi, TOUT='OUI'),
),
UNITE=80)
We tried all the possible combinations (eg. ELGA, ELEM, ELNO and finaly NOEU) but none of them worked. The TYPE_CHAM='NOEU_SOUR_F' create the field (CREA_CHAMP works) but in this case the IMPR_RESU produces the following error:
CR d'execution de JDC en MIXTE
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
! <S> Exception utilisateur levee mais pas interceptee. !
! Les bases sont fermees. !
! Type de l'exception : error !
! !
! Erreur de programmation : Nom de grandeur inattendu : SOUR_F !
! Routine : IRCMVA !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
fin CR d'execution de JDC en MIXTE
all the others (ELGA, ELEM, ...) produce error at the CREA_CHAMP:
CR d'execution de JDC en MIXTE
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
! <S> Exception utilisateur levee mais pas interceptee. !
! Les bases sont fermees. !
! Type de l'exception : error !
! !
! il n y a pas de paramètre INOUT associe a la grandeur: SOUR_F dans l option: !
! TOU_INI_ELGA !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
fin CR d'execution de JDC en MIXTE
We tried other possibilities as well, eg. TYPE_CHAM='ELGA_NEUT_F', but all of them produced various errors.
Do we miss something? Is it possible in aster at all?
(Minimal example attached, the code runs without the field creation, the numbers (eg. material parameters) does not really have physical meaning)
Thank you for your help!
dezsit
Offline
Pages: 1