Sierra Toolkit Version of the Day
Todo List

Member stk::all_write_string (ParallelMachine, std::ostream &, const std::string &)
REFACTOR The per-processor separator needs to be addressed. Already created a duplicate for deferred error messages which could be replacement.

Class stk::CSet
REFACTOR Use smart pointers to avoid destruction issue.

Member stk::io::field_data_from_ioss (const stk::mesh::FieldBase *field, std::vector< stk::mesh::Entity * > &entities, Ioss::GroupingEntity *io_entity, const std::string &io_fld_name)
REFACTOR Need some additional compatability checks between Ioss field and stk::mesh::Field; better error messages...

Member stk::io::field_data_to_ioss (const stk::mesh::FieldBase *field, std::vector< stk::mesh::Entity * > &entities, Ioss::GroupingEntity *io_entity, const std::string &io_fld_name, Ioss::Field::RoleType filter_role)
REFACTOR Need some additional compatability checks between Ioss field and stk::mesh::Field; better error messages...

Member stk::io::internal_part_processing (Ioss::EntityBlock *entity, stk::mesh::MetaData &meta)

IMPLEMENT Determine whether application can work with this topology type... Perhaps map_topology_ioss_to_cell only returns a valid topology if the application has registered

IMPLEMENT handle cell_topolgy mapping error...

Member stk::io::map_topology_ioss_to_cell (const Ioss::ElementTopology *topology)

QUESTION Should this function be at the application level, or provided by stk_io? In either case, applications should have capabilty to register new mappings.

REFACTOR Consider either using or integrating the Trilinos CellTopology package into or with the Ioss::ElementTopology classes. That would then totally eliminate the need for these fragile mapping functions. However, it would still need to be extensible via application registration of new type mappings.

Member stk::mesh::fem::FEMMetaData::get_part (const std::string &p_name, const char *required_by=NULL) const
REFACTOR remove required_by argument

Class stk::mesh::FullTensor36
REFACTOR Where should FullTensor live, in the application, in the toolkit or a common application header?

Class stk::mesh::GatherField< F, R >
REFACTOR This convenience class is not appropriately named.

Member stk::mesh::MetaData::declare_attribute_with_delete (Part &part, const T *attribute)
REFACTOR Should be using a shared pointer in this interface. declare_attribute( Part & , shared_ptr<const T> & );

Member stk::mesh::MetaData::declare_attribute_with_delete (FieldBase &field, const T *attribute)
REFACTOR Should be using a shared pointer in this interface.

Member stk::mesh::MetaData::get_part (const std::string &p_name, const char *required_by=NULL) const
REFACTOR remove required_by argument

Class stk::mesh::SymmetricTensor33
REFACTOR Where should SymmetricTensor live, in the application, in the toolkit or a common application header?

Member stk::ParallelDatatype
REFACTOR: Figure out a better way to typedef for non-MPI builds

Member stk::ParallelMachine
REFACTOR: Figure out a better way to typedef for non-MPI builds

Member stk::report_deferred_messages (ParallelMachine comm)
REFACTOR Should the message counts be broadcast to the other processors?

Class stk::StaticAssert< expression >
REFACTOR Does StaticAssert belong here? Anywhere?

Member stk_example_io::io_example (stk::ParallelMachine comm, const std::string &in_filename, const std::string &out_filename)

REFACTOR A real app would register a subset of the fields on the mesh database as fields that the app would want read at one or all or specified steps. In this example, all fields existing on the input mesh database are defined on the parts in the stk::mesh.

IMPLEMENT handle error... Possibly an assert since I think the corresponding entity should always exist...

IMPLEMENT handle error... Possibly an assert since I think the corresponding entity should always exist...

Member stk_example_io::process_elementblocks (Ioss::Region &region, stk::mesh::MetaData &meta)

IMPLEMENT truly handle attribute fields... For this case we are just defining a field for each attribute field that is present in the mesh...

IMPLEMENT truly handle fields... For this case we are just defining a field for each transient field that is present in the mesh...

IMPLEMENT truly handle fields... For this case we are just defining a field for each transient field that is present in the mesh...

Member stk_example_io::process_input_request (Ioss::Region &region, stk::mesh::BulkData &bulk, int step)

REFACTOR Need filtering mechanism.

IMPLEMENT handle error... Possibly an assert since I think the corresponding entity should always exist...

IMPLEMENT handle error... Possibly an assert since I think the corresponding entity should always exist...

Member stk_example_io::process_nodeblocks (Ioss::Region &region, stk::mesh::BulkData &bulk)
REFACTOR Application would probably store this field (and others) somewhere after the declaration instead of looking it up each time it is needed.

Member stk_example_io::process_nodeblocks (Ioss::Region &region, stk::mesh::MetaData &meta)
IMPLEMENT truly handle fields... For this case we are just defining a field for each transient field that is present in the mesh...

Member stk_example_io::process_nodesets (Ioss::Region &region, stk::mesh::BulkData &bulk)
REFACTOR Application would probably store this field (and others) somewhere after the declaration instead of looking it up each time it is needed.

Member stk_example_io::process_nodesets (Ioss::Region &region, stk::mesh::MetaData &meta)

REFACTOR should "distribution_factor" be a default field that is automatically declared on all objects that it exists on as is done in current framework?

REFACTOR How to associate distribution_factors field with the nodeset part if a node is a member of multiple nodesets

IMPLEMENT truly handle fields... For this case we are just defining a field for each transient field that is present in the mesh...

REFACTOR How to associate distribution_factors field with the nodeset part if a node is a member of multiple nodesets

IMPLEMENT truly handle fields... For this case we are just defining a field for each transient field that is present in the mesh...

Member stk_example_io::process_output_request (Ioss::Region &region, stk::mesh::BulkData &bulk, int step)

REFACTOR Need filtering mechanism.

IMPLEMENT handle error... Possibly an assert since I think the corresponding entity should always exist...

IMPLEMENT handle error... Possibly an assert since I think the corresponding entity should always exist...

Member stk_example_io::process_surface_entity (Ioss::SideSet *sset, stk::mesh::MetaData &meta, stk::mesh::EntityRank sset_rank)
IMPLEMENT truly handle fields... For this case we are just defining a field for each transient field that is present in the mesh...
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Friends