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

Ticket #2341 (closed enhancement: fixed)

Opened 8 years ago

Last modified 4 years ago

Fine-grain management of evaluations

Reported by: wehart Owned by: jdsiiro
Priority: normal Milestone: Acro 2.1
Component: Colin Version: Colin 2.0
Keywords: Cc:
Subcomponent: Source Code

Description (last modified by wehart) (diff)

Control evaluations of objectives/constraints/gradients in Coliny solvers at a finer granluarity to better manage the use of expensive/cheap evaluations.

Here's a note from Mike Eldred:

If you want to fully support the application-specific nature of combined vs. separated objective/constraint evals and combined vs. separated val/grad/Hessian evals, then you could go so far as to flexibly support each possibility in your algorithm design (although the separated/separated and combined/combined options seem the most useful) and let the user select the more efficient approach. For DAKOTA, my default would be combined/combined, but there are definitely cases where other settings would be more efficient by avoiding unneeded calculations. This design may be unrealistic if you have lots of algorithms from different sources, but would seem to have good payoff if practical.

Pam Williams is working on supporting exactly this capability within
OPT++ for combined/separated val/grad/Hessians (am internal OPT++ mode
override option). For objective/constraint combinations, OPT++ can't readily support this so we're doing combinations in the wrapper.

Attachments

Change History

comment:1 Changed 6 years ago by wehart

  • Description modified (diff)
  • Component changed from Coliny to Colin
  • Priority changed from high to normal
  • Version changed from 2.0 to Colin 2.0
  • Milestone set to Colin 3.1
  • Owner changed from wehart to jdsiiro
  • Type changed from defect to enhancement

I think the key issue here is how the user can denote that different aspects of a code are cheap/expensive.

comment:2 Changed 6 years ago by jdsiiro

  • severity normal deleted

Converting all severities into priorities and deprecating the severity field.

comment:3 Changed 5 years ago by jdsiiro

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

I think the intent behind this ticket was to support *both* separate and "simultaneous" evaluation of (F, grad, Hessian). COLIN supports this through the EvalX() and Request_X() family of Application methods.

Annotating application components (i.e. cheap/expensive) is a separate issue (#4372).

comment:4 Changed 4 years ago by jdsiiro

  • Milestone changed from Colin 3.1 to Acro 2.1

Milestone Colin 3.1 deleted

View

Add a comment

Modify Ticket

Change Properties
<Author field>
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.