ffc team mailing list archive

["Garth N. Wells" <gnw20@xxxxxxxxx>]

Anders Logg wrote:
> On Mon, Feb 01, 2010 at 09:45:02AM +0000, Garth N. Wells wrote:
>>
>> Anders Logg wrote:
>>> I have simplified the access to form compiler parameters from DOLFIN.
>>> Here's a summary.
>>>
>>> 1. 'options' --> 'parameters' in FFC
>>>
>>> 2. DOLFIN stores form compiler parameters in parameters["form_compiler"]
>>> and the values are easily accessible by
>>>
>>>   info(parameters, True)
>>>
>>> or
>>>
>>>   info(parameters["form_compiler"])
>>>
>>> 3. DOLFIN reads the default values at startup by calling
>>>
>>>   form_compiler.default_parameters()
>>>
>>> 4. The 'options' parameter to jit, assemble and Form have has been
>>> renamed 'form_compiler_parameters'.
>>>
>>> 5. Before calling the form compiler, DOLFIN first reads the global
>>> parameters from parameters["form_compiler"], then overrides the values
>>> with any local values provided by the form_compiler_parameters
>>> argument.
>>>
>>> 6. To see more output from the form compiler, *decrease* the log level
>>> of the form compiler by form example setting it to INFO:
>>>
>>>   parameters["form_compiler"]["log_level"] = INFO
>>>
>>> This is the default log level in FFC, but DOLFIN changes it to INFO + 5
>>> at startup to hide messages from the form compiler by default.
>>>
>>> Have a go and see if it works as expected.
>>>
>> Doesn't look to me that FFC is picking up the parameters via, for example,
>>
>>   parameters["form_compiler"]["cpp_optimize"] = True
>>
>> I can take a look, but it won't be for a while.
> 
> Should be fixed now.
>

Thanks. Looks good now.

Garth

> --
> Anders