Error message

  • Deprecated function: Return type of DatabaseStatementBase::execute($args = [], $options = []) should either be compatible with PDOStatement::execute(?array $params = null): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2244 of /vz/drupal/drupal-7.23/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /vz/drupal/drupal-7.23/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /vz/drupal/drupal-7.23/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /vz/drupal/drupal-7.23/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /vz/drupal/drupal-7.23/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /vz/drupal/drupal-7.23/includes/database/database.inc).

WP3/4/5 Kick-Off Meeting, 14th-15th March 2017 in Düsseldorf (BFI)

The goal of this meeting was to start the “WP3.Architecture”, “WP4.Modelling” and “WP5. Optimization and implementation” efficiently, reviewing in detail the planned activities for each work package and the interaction plan between them in order to develop the COCOP solution.These WPs are all connected requiring and providing input for each other. In order to facilitate a successful development, an iterative approach will be followed. Each cycle will start with defining the goals and necessary corrections, followed by independent work of the work packages, and ending with an evaluation event where results are communicated and cross-validated.

Consortium photograph

 Click here to go back to COCOP's project meetings.