RE: RE: Re: DLOAD subroutine not working on parallel mode Yahoo / Sent

"David Lindeman [email protected] [Abaqus]" <[email protected]> Fri, 10 May 2019 14:02:18 +0000
Newsgroups gmane.comp.mathematics.abaqus.user
Message-ID <DM6PR03MB3435AA1DDA7E1B8183F0E53CE10C0@DM6PR03MB3435.namprd03.prod.outlook.com>
All nodes and elements are renumbered during the solution phase (since unique reference numbers are needed).  The mapping between these “globall” numbers and the “local” (i.e.,  part instance name and node number) can be obtained using the GETPARTINFO/VGETPARTINFO and GETINTERNAL/VGETINTERNAL utility routines.

Regards,

Dave Lindeman
Staff Scientist
Corporate Research Systems Laboratory
3M Center 235-3G-08
St. Paul, MN 55144
651-733-6383

From: [email protected] <[email protected]>
Sent: Thursday, May 09, 2019 4:07 AM
To: [email protected]
Subject: [EXTERNAL] RE: Re: [Abaqus] DLOAD subroutine not working on parallel mode Yahoo / Sent



Hi,

I have a small issue and since its connected with subroutine I would like some help. In my model I have now added acoustic element as a separate part and created an instance from the meshed part. When I run the same DLOAD subroutine it does not run properly. I found out that now when I add the acoustic part in the instance and run the analysis, even if I do not connect it by tie or anything, Abaqus is changing the element numbers and giving unique element numbers. I read about this in Users guide 4.1.1 output section too.
My pressure file has the element numbers from the .inp file on the surface but in the new model it renumbers it from 190000 or something. I tried to renumber the acoustic elements and nodes but no change. How can I stop this from happening so that when I call NOEL in DLOAD it is possible to map the pressure on the correct NOEL as per .inp file?

Arun





________________________________



3M Notice: This communication is from an [EXTERNAL] sender.
If this email looks suspicious, do NOT click or open any links or attachments in the email. To report a suspicious email, click on the Report Phishing – PhishMe icon in the Outlook ribbon or forward this email using the report email as spam link in the text below.

Click here<https://spam.mmm.com/pem/pages/digestProcess/digestProcess.jsf?content=aedaaa864ecbae9470642dc0e6829f2773c0e0e6ab7740fb70e80d0c9c36d891c6c4ff5fb22097b592aab29dac82584f30f60c161a797f8d8d8a621478a2f25250f75f3a4b570e12125b08ef0dd8e5d1dbc7a045714a146255659761471276b9c37b570f20a98a734732948327931bff0875daa5917e63d486fb3ae9624af57a17d051a1b719785d> to report this email as spam





[Non-text portions of this message have been removed]