[Devel] DAKOTA Users Mailing List

I obtained the following errors when building DAKOTA on medusa,

make[4]: lex: Command not found
make[4]: *** [/home/vinayrao/Dakota/VendorPackages/idr/i686-unknown-linux/idr-gen.o] Error 127
make[3]: *** [idrtest] Error 2
make[2]: *** [install] Error 2
make[3]: pgf90: Command not found
make[3]: *** [/home/vinayrao/Dakota/VendorOptimizers/LHS/i686-unknown-linux/Parms.o] Error 127
make[2]: *** [install] Error 2
make[1]: *** [build] Error 2
cc1plus: note: -fwritable-strings is deprecated; see documentation for details
keywordtable.C:22:25: idr-keyword.h: No such file or directory
keywordtable.C:525: error: elements of array `const KeywordHandler idrKeywordTable[]' have incomplete type
keywordtable.C:525: error: uninitialized const `idrKeywordTable'
keywordtable.C:525: error: storage size of `idrKeywordTable' isn't known
make[2]: *** [/home/vinayrao/Dakota/src/i686-unknown-linux/keywordtable.o] Error 1
make[1]: *** [install] Error 2
/usr/bin/ld: cannot find -lfl
collect2: ld returned 1 exit status
make[2]: *** [/home/vinayrao/Dakota/test/i686-unknown-linux/text_book] Error 1
make[1]: *** [install] Error 2
cp: cannot stat `/home/vinayrao/Dakota/src/i686-unknown-linux/dakota': No such file or directory
cp: cannot stat `/home/vinayrao/Dakota/src/i686-unknown-linux/dakota_restart_util': No such file or directory
cp: cannot stat `/home/vinayrao/Dakota/src/i686-unknown-linux/libdakota.a': No such file or directory
cp: cannot stat `/home/vinayrao/Dakota/VendorPackages/idr/i686-unknown-linux/libidr.a': No such file or directory
cp: cannot stat `/home/vinayrao/Dakota/VendorOptimizers/LHS/i686-unknown-linux/liblhs.a': No such file or directory

We need to install Flex on medusa,
http://howtos.linux.com/guides/html/appendixa/flex.shtml

Fortran 90 compiler has to be installed. I am getting some linker errors (collect2: ld returned 1 exit status) and install errors.

after all the packages (selected ones) have been successfully compiled, the main "dakota" executable will be created. I am not able to understand the Install and Build errors. Any help will be appreciated,

Thanks,
Vinay Rao

I saw following documentation in one of the parallel library files,

Command line arguments can be very problematic (more so with mpirun than yod). The following procedures for maintaining serial and parallel capability in a single executable are being considered:

(a) always invoking MPI_Init, even for an executable launched serially (no mpirun),

(b) trigger conditional MPI initialization with a separate command line argument (-mpi, this avoids GetLongOpt::parse problems), and

(c) invoking GetLongOpt::parse first so that problem_db settings can be used for conditional invocation of MPI_Init in init_parallel_lib.

The first case works with MPICH on Sun (although there have been problems with path designations to input files) and it will be fine for TFLOP by default since we will never invoke cougar dakota w/o yod; however, it does not appear to work for Digital MPI on the Dec.

The second case will be retained as a possible backup and its design merits should be considered vs. those of the parallel_library IDR input specification.

The last case fails since MPI args cause GetLongOpt::parse errors for unenrolled options, the subsequent condition of argc and argv passed to MPI_Init is currently unknown, and the standard MPI implementation behavior is being violated.

MPICH does add "-p4pg" (master) and "-p4amslave" (slaves) command line
arguments which can be used for detection; however other platforms with proprietary MPI implementations (e.g., DEC, SGI) pass no telltale argv content. On DEC/SGI, it's necessary to query environment variables,

e.g. DIGITALMPI_ENV_MAP, MPI_ENVIRONMENT. These variables are set for all processors on DEC/SGI, but again it is not consistent across platforms (MPICH sets MPIRUN_DEVICE=ch_p4, but only on the master processor).

Thanks,
Vinay Rao

I goal isn't really to get greater access than others to the dakota team.
:)

Usually a project will have a few public lists (eg. announce, users, and
devel) and any number of private lists. some projects don't expose their
devel lists to the public though.

This seems to be the case with dakota. They seem to just want all external
communication to go on the "users" list. This is fine and very common.
All it means is that we should use this list when communicating with the
dakota folks.

If we don't get any responses then they are either busy or not very
responsive. Unless the issues is something really important, we shouldn't
try to hunt down contacts with the dakota folks through other means.
"Which MPI did you build against" doesn't fall under "really important"
though.

We should only use their official communication lists (dakota-users)
that they set up to support the dakota community.

~jpr

On Fri, 13 Jan 2006, Vinay Nagaraja Rao wrote:

> Users mailing list in DAKOTA is managed by Majordomo mailing list
> software.
>
> Following users lists are available in it:
>
> dakota-users
> mdo_forum
> mdotc_private
> mdotc_public
> opt-info
> opt-research
> test-endo
>
> Most of those lists are inactive or no index was found.
>
> I found the below two links after subscribing to those lists:
>
> http://endo.sandia.gov/DAKOTA/lists.html
>
> http://endo.sandia.gov/AIAA_MDOTC/forum/MDOTC_forum.html
>
> The dakota developers list is for internal use by the DAKOTA development
> team and has restricted access.
>
> I have to get information through dakota@sandia.gov and other project
> members of dakota.
>
> Thanks,
> Vinay Rao
>
>