Plain handler

This forum is for issues related to parallel processing
and OpenSees using the new interpreters OpenSeesSP and OpenSeesMP

Moderator: selimgunay

Post Reply
kyungtae79
Posts: 27
Joined: Fri Sep 14, 2007 12:17 pm
Location: UCSD

Plain handler

Post by kyungtae79 » Wed Jan 13, 2010 11:52 am

Hello, all

I used 'equalDOF' using OpenSeesSP.
The constraints is used by Plain.

Then, I got the message following like:


WARNING PlainHandler::handle() - constraint at dof 4 already specified for constrained node in MP_Constraint at node 170400

Is the reason that I used 'Plain constraints'?

fmk
Site Admin
Posts: 5883
Joined: Fri Jun 11, 2004 2:33 pm
Location: UC Berkeley
Contact:

Post by fmk » Sat Jan 16, 2010 9:37 am

is node 170400 involved in a constraiint already?

kyungtae79
Posts: 27
Joined: Fri Sep 14, 2007 12:17 pm
Location: UCSD

Post by kyungtae79 » Sun Jan 17, 2010 5:30 pm

I used that node (170400) using 'equalDOF' to connect another node at the same location.

There is another question about 'recorder'.

I am using OpenSeesSP for my model.

I used recorder command of 'recorder file -xml bridge_nodes.txt...'.,

However, as I ran my scripts,
I got responses associated with some of nodes which I am interested in.
(e.g. I want to get results from nodes of 1,2,3,4,..10, however, I just got it from 2,3 nodes)

Or, I got nothing from that run.

Do you know how to get all responses?

Or, is there a way I can control the recorder?

- Here is my guess.

I just guess that the main run would be terminated before other runs are finished.
then, the outfile could not collect the information from other computation.

fmk
Site Admin
Posts: 5883
Joined: Fri Jun 11, 2004 2:33 pm
Location: UC Berkeley
Contact:

Post by fmk » Tue Jan 19, 2010 11:50 am

on the destruction of the recorders the processes do some sends & recvs on the data in the files .. can you try issuing the command remove recorders before the end of your script to see if the problem still occurs.

kyungtae79
Posts: 27
Joined: Fri Sep 14, 2007 12:17 pm
Location: UCSD

Post by kyungtae79 » Tue Jan 19, 2010 12:30 pm

I don't understand very well.

What you mean is..
to put the command out not to work the recorder.
then see how it is going on?

If I put the command there,
how can I check whether or not the recorder files will collect information?

fmk
Site Admin
Posts: 5883
Joined: Fri Jun 11, 2004 2:33 pm
Location: UC Berkeley
Contact:

Post by fmk » Tue Jan 19, 2010 12:43 pm

no .. put the command remove recorders on the last line of your script.

kyungtae79
Posts: 27
Joined: Fri Sep 14, 2007 12:17 pm
Location: UCSD

Post by kyungtae79 » Tue Jan 19, 2010 12:46 pm

Is the command remove recorder
exactly "remove recorder"?

I can not look it up on the manual.

fmk
Site Admin
Posts: 5883
Joined: Fri Jun 11, 2004 2:33 pm
Location: UC Berkeley
Contact:

Post by fmk » Tue Jan 19, 2010 1:16 pm

no .. it is "remove recorders"

kyungtae79
Posts: 27
Joined: Fri Sep 14, 2007 12:17 pm
Location: UCSD

Post by kyungtae79 » Wed Jan 20, 2010 12:37 pm

As you recommended, I put the "remove recorders" in the end of my scripts.

However, I still got some lack of output.

(From 3000 steps, I just got results of 243 steps.)

BlueLotus
Posts: 2
Joined: Wed Oct 23, 2013 1:15 am

Re: Plain handler

Post by BlueLotus » Sat Nov 23, 2013 3:23 am

The node 170400 is also involved in the constraint. I have used this node many times.

The term 'recorder' was what I wanted to know and thanks for the details you have shared here. I am also using OpenSeesSP, but never had to use the option recorder. Thanks for sharing.



Tech support

Post Reply