This file is indexed.

/usr/include/deal.II/numerics/data_component_interpretation.h is in libdeal.ii-dev 8.1.0-4.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
// ---------------------------------------------------------------------
// $Id: data_component_interpretation.h 30036 2013-07-18 16:55:32Z maier $
//
// Copyright (C) 2007 - 2013 by the deal.II authors
//
// This file is part of the deal.II library.
//
// The deal.II library is free software; you can use it, redistribute
// it, and/or modify it under the terms of the GNU Lesser General
// Public License as published by the Free Software Foundation; either
// version 2.1 of the License, or (at your option) any later version.
// The full text of the license can be found in the file LICENSE at
// the top level of the deal.II distribution.
//
// ---------------------------------------------------------------------

#ifndef __deal2__data_component_interpretation_h
#define __deal2__data_component_interpretation_h



#include <deal.II/base/config.h>

DEAL_II_NAMESPACE_OPEN

/**
 * A namespace solely for the declaration of the
 * DataComponentInterpretation::DataComponentInterpretation enum.
 */
namespace DataComponentInterpretation
{
  /**
   * The members of this enum are used to
   * describe the logical interpretation of
   * what the various components of a
   * vector-valued data set mean. For
   * example, if one has a finite element
   * for the Stokes equations in 2d,
   * representing components $(u,v,p)$, one
   * would like to indicate that the first
   * two, $u$ and $v$, represent a logical
   * vector so that later on when we
   * generate graphical output we can hand
   * them off to a visualization program
   * that will automatically know to render
   * them as a vector field, rather than as
   * two separate and independent scalar
   * fields.
   *
   * By passing a set of enums of the
   * current kind to the
   * DataOut_DoFData::add_data_vector
   * functions, this can be achieved.
   *
   * See the step-22 tutorial
   * program for an example on how this
   * information can be used in practice.
   *
   * @author Wolfgang Bangerth, 2007
   */
  enum DataComponentInterpretation
  {
    /**
     * Indicates that a component of a
     * data set corresponds to a scalar
     * field independent of the others.
     */
    component_is_scalar,

    /**
     * Indicates that a component of a
     * data set is part of a
     * vector-valued quantity.
     */
    component_is_part_of_vector
  };
}


DEAL_II_NAMESPACE_CLOSE

#endif