04-07-2013
I am getting concerned that our compiled Boost-code is getting bloated. We will be experimenting with basic C++ functions as if there was only one core and no Boost, then add MPI pragmas to the C++ code and finally add user functionality (screens, post-processing etc) in Python.
7 More Discussions You Might Find Interesting
1. Programming
i have made a ftp application in socket programming which uses TCP/IP .. i have the problem runing the only problem is on the client side i take the user input for the file to be downloaded from the command promt.
write(s, argv, strlen(argv)+1); // this is how i write in client side
argv is... (1 Reply)
Discussion started by: toughguy2handle
1 Replies
2. Programming
HI
For the past 1 week i have been trying to include the concepts of parallel programming or thread in the sniffex.c code. Haven't been able to..
Please suggest sm appropriate modifications to the following code:
/*
* sniffex.c
*
* Sniffer example of TCP/IP packet capture using... (1 Reply)
Discussion started by: aka.bhagvanji
1 Replies
3. Debian
I do some Python programming in windows, understand how to use python in windows... However I do not know how to use python in Linux. I do know the commands n such are the same but there isn't any IDLE or anything its ran straight from the terminal by typing python but I have never used python that... (2 Replies)
Discussion started by: Cryptek
2 Replies
4. UNIX for Advanced & Expert Users
Hi.
Has anyone here got an experience doing conversion from asn1 format to a readable format so that it can be processed by Oracle? I want to load the data into a table. This is a CDR file.
Attached is the pairing file. Please remove the .txt at the end.
Someone said that it is possible... (1 Reply)
Discussion started by: aimy
1 Replies
5. Shell Programming and Scripting
Hi.
Has anyone here got an experience doing conversion from asn1 format to a readable format so that it can be processed by Oracle? I want to load the data into a table. This is a CDR file.
Attached is the pairing file. Please remove the .txt at the end.... (1 Reply)
Discussion started by: aimy
1 Replies
6. Shell Programming and Scripting
Hello,
I have a 4 core machine.
Here is my initial script
cd /work/
python script.py input.txt output.txt 1 2 3
This script runs for 1.5hrs.
So I read across the web and figured out that you can use GNU parallel to submit multiple jobs using parallel. But I am not sure if I can run... (4 Replies)
Discussion started by: jacobs.smith
4 Replies
7. UNIX for Beginners Questions & Answers
I have created the python application, which was deployed on UNIX server but due to some certain issues I have to redeploy the application every time while logging in to the server
I am trying to make it work permanently on that server even when I am not using the UNIX server also
Any... (1 Reply)
Discussion started by: varul29
1 Replies
LEARN ABOUT DEBIAN
mpi_add_error_code
MPI_Add_error_code(3) MPI MPI_Add_error_code(3)
NAME
MPI_Add_error_code - Add and MPI error code to an MPI error class
SYNOPSIS
int MPI_Add_error_code(int errorclass, int *errorcode)
INPUT PARAMETER
errorclass
- Error class to add an error code.
OUTPUT PARAMETER
errorcode
- New error code for this error class.
THREAD AND INTERRUPT SAFETY
This routine is thread-safe. This means that this routine may be safely used by multiple threads without the need for any user-provided
thread locks. However, the routine is not interrupt safe. Typically, this is due to the use of memory allocation routines such as malloc
or other non-MPICH runtime routines that are themselves not interrupt-safe.
NOTES FOR FORTRAN
All MPI routines in Fortran (except for MPI_WTIME and MPI_WTICK ) have an additional argument ierr at the end of the argument list. ierr
is an integer and has the same meaning as the return value of the routine in C. In Fortran, MPI routines are subroutines, and are invoked
with the call statement.
All MPI objects (e.g., MPI_Datatype , MPI_Comm ) are of type INTEGER in Fortran.
ERRORS
All MPI routines (except MPI_Wtime and MPI_Wtick ) return an error value; C routines as the value of the function and Fortran routines in
the last argument. Before the value is returned, the current MPI error handler is called. By default, this error handler aborts the MPI
job. The error handler may be changed with MPI_Comm_set_errhandler (for communicators), MPI_File_set_errhandler (for files), and
MPI_Win_set_errhandler (for RMA windows). The MPI-1 routine MPI_Errhandler_set may be used but its use is deprecated. The predefined
error handler MPI_ERRORS_RETURN may be used to cause error values to be returned. Note that MPI does not guarentee that an MPI program can
continue past an error; however, MPI implementations will attempt to continue whenever possible.
MPI_SUCCESS
- No error; MPI routine completed successfully.
MPI_ERR_OTHER
- Other error; use MPI_Error_string to get more information about this error code.
LOCATION
add_error_code.c
5/20/2010 MPI_Add_error_code(3)