Comments you submit will be routed for moderation. If you have an account, please log in first.
Modify

Ticket #4118 (closed enhancement: fixed)

Opened 2 years ago

Last modified 22 months ago

installation issues with 5.2

Reported by: elaine.hale@… Owned by: wjbohnh
Priority: normal Milestone:
Component: Porting/Distribution Version:
Severity: normal Keywords:
Cc: briadam, dmvigi, wjbohnh Due Date:
Parent Tickets: Blocked By:
Blocking: Requestor:
Sensitive: no

Description

The OpenStudio? project (LGPL, cross-platform project for building energy modeling and analysis) is starting to use DAKOTA. However, to migrate to version 5.2, we will need binary windows packages. Building DAKOTA seems to require a Fortran compiler, which is not readily available on Windows.

On a related note, the Mac binaries seem to have some odd paths hard coded into them that do not necessarily work for all users. (Users/dakota/...) Also, our preferred Linux OS is Ubuntu, not Red Hat. However, at least for version 5.1 building on Ubuntu was not too difficult--I will keep you updated.

Subtickets

#4123: dakota version 5.2 executable not able to find libdakota_src.so on ubuntusupportclosedwjbohnh

Attachments

Change History

comment:1 Changed 2 years ago by briadam

  • Cc briadam, dmvigi, wjbohnh added
  • Type changed from defect to enhancement

Hi Elaine,

  • We are working on Windows binaries for 5.2, but suspect we may have to issue a patch release soon. We are also working toward MSVS builds of DAKOTA this new year.
  • Thanks for the note about the relative paths in Mac binaries. Unfortunately we build with custom installed gcc compilers and the autotools end up with a lot of relative paths. If you find setting DYLD_LIBRARY_PATH to include Dakota/bin doesn't work for you, please let us know.
  • If you generate tips for building on Ubtuntu, we can add them to our Wiki pages. We haven't had a ton of problems in the past, though some anomalies.

Brian

comment:2 in reply to: ↑ description Changed 2 years ago by wjbohnh

Replying to elaine.hale@…:

...
... Also, our preferred Linux OS is Ubuntu, not Red Hat. However, at least for version 5.1 building on Ubuntu was not too difficult--I will keep you updated.

Thanks. Please keep us updated; as an FYI, an external contributor performs nightly DAKOTA(public) builds on an older ubuntu host. Here is his CMake/CTest/CDash setup, in case it is of value to you:

cmake_minimum_required(VERSION 2.8)
set(CTEST_SITE "jdhost.company.com")
set(CTEST_BUILD_NAME "gcc 4.1.3 x64 Release")
set(CTEST_NOTES_FILES "${CTEST_SCRIPT_DIRECTORY}/${CTEST_SCRIPT_NAME}")

set(CTEST_DASHBOARD_ROOT "/home/jd/dashboards")
set(CTEST_SOURCE_DIRECTORY "${CTEST_DASHBOARD_ROOT}/Dakota-src")
set(CTEST_BINARY_DIRECTORY "${CTEST_DASHBOARD_ROOT}/Dakota-bin")

set(CTEST_UPDATE_COMMAND "/home/jd/dashboards/Support/svn/bin/svn")
set(CTEST_CMAKE_GENERATOR "Unix Makefiles")
set(CTEST_BUILD_CONFIGURATION Release)
set(CTEST_BUILD_COMMAND "make -i -j9" )

CTEST_EMPTY_BINARY_DIRECTORY(${CTEST_BINARY_DIRECTORY})

# Write initial cache.
file(WRITE "${CTEST_BINARY_DIRECTORY}/CMakeCache.txt"
  "Boost_INCLUDE_DIR:PATH=/home/jd/dashboards/Support/boost_install/include")

ctest_start(Nightly)
ctest_update(SOURCE "${CTEST_SOURCE_DIRECTORY}")
ctest_configure(BUILD "${CTEST_BINARY_DIRECTORY}")
ctest_build(BUILD "${CTEST_BINARY_DIRECTORY}")
ctest_test(BUILD "${CTEST_BINARY_DIRECTORY}")
ctest_submit()

comment:3 follow-up: ↓ 4 Changed 2 years ago by elaine.hale@…

Thanks, all! We will keep you posted. Does the external contributor have a webpage with his dashboard/packages?

Elaine

comment:4 in reply to: ↑ 3 Changed 2 years ago by wjbohnh

Replying to elaine.hale@…:

Thanks, all! We will keep you posted. Does the external contributor have a webpage with his dashboard/packages?

Well, we're still relatively new to the CMake/CTest/CDash world, and it is very minimal, so we're not truly ready to start advertising it yet. But if you're willing to provide feedback to help us get better (and don't mind keeping it on the down-low for now) here is website with our CDashboard:
http://dakota.sandia.gov/cdash/index.php?project=Dakota

Further, in case you're not aware, some lower-level packages (LAPACK, Boost, Pecos) have CDashboards hosted at the Kitware CDash site:
 http://my.cdash.org/index.php

comment:5 Changed 2 years ago by elaine.hale@…

Cool, thanks for sharing! We also use CMake/CTest/CDash, so we can try to provide feedback. I am not the expert on that side of our project, though. Those people are Kyle Benne (kyle.benne@…) and Alex Swindler (alex.swindler@…). We have also worked directly with KitWare?, and have set up a Radiance dashboard. (The OpenStudio? dashboard is at  http://my.cdash.org/index.php?project=OpenStudio. Please excuse the mess--we have some build machine issues at the moment. And the project website is  http://openstudio.nrel.gov.)

comment:6 Changed 2 years ago by wjbohnh

  • Status changed from new to accepted

As far a the Mac binaries go, might find the info in a related ticket useful:
 https://software.sandia.gov/trac/dakota/ticket/4052

That said, I still recommend building from source for Mac platforms. Please note the that DAKOTA MacOSX build host is rather old and still runs the Leopard OS.

comment:7 in reply to: ↑ description Changed 22 months ago by wjbohnh

Replying to elaine.hale@…:

The OpenStudio? project ...
... Building DAKOTA seems to require a Fortran compiler, which is not readily available on Windows.

Perhaps after reading Bill Hoffman's blog post, you'll feel more at-ease with DAKOTA's approach to managing fortran dependencies on Windows:
 http://www.kitware.com/blog/home/post/231

I hope that helps.. I believe DAKOTA is well beyond the point of being able to build on a platform that does NOT have a fortran compiler. "Readily available" could be debated, but the bottom-line is that I don't see that pre-requisite going, so it-is-what-it-is.

Best of luck.
--Bill

comment:8 in reply to: ↑ description Changed 22 months ago by wjbohnh

  • Status changed from accepted to closed
  • Resolution set to fixed

Replying to elaine.hale@…:

... the Mac binaries seem to have some odd paths hard coded into them that do not necessarily work for all users. (Users/dakota/...) ...

I am hopeful that Brian's tip wrt DYLD_LIBRARY_PATH resolved the Mac binary installation issue. FYI, an additional resource for customers needing environment setup help was recently added to the DAKOTA wiki:
 https://software.sandia.gov/trac/dakota/wiki/EnvironmentSetup

I hope that closing this ticket is OK. Please create new ticket(s) if additional support on platform-specific installation issues is neeeded.

View

Add a comment

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.