- Member stk_classic::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_classic::Copy< n, i >
- REFACTOR: Add a sub-namespace?
- Class stk_classic::CSet
- REFACTOR Use smart pointers to avoid destruction issue.
- Member stk_classic::io::field_data_from_ioss (const stk_classic::mesh::FieldBase *field, std::vector< stk_classic::mesh::Entity *> &entities, Ioss::GroupingEntity *io_entity, const std::string &io_fld_name)
- REFACTOR Need some additional compatability checks between Ioss field and stk_classic::mesh::Field; better error messages...
- Member stk_classic::io::field_data_to_ioss (const stk_classic::mesh::FieldBase *field, std::vector< stk_classic::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_classic::mesh::Field; better error messages...
- Member stk_classic::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_classic::mesh::fem::FEMMetaData::get_part (const std::string &p_name, const char *required_by=NULL) const
- REFACTOR remove required_by argument
- Class stk_classic::mesh::FullTensor36
- REFACTOR Where should FullTensor live, in the application, in the toolkit or a common application header?
- Class stk_classic::mesh::GatherField< F, R >
- REFACTOR This convenience class is not appropriately named.
- Member stk_classic::mesh::MetaData::declare_attribute_with_delete (FieldBase &field, const T *attribute)
- REFACTOR Should be using a shared pointer in this interface.
- Member stk_classic::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_classic::mesh::MetaData::get_part (const std::string &p_name, const char *required_by=NULL) const
- REFACTOR remove required_by argument
- Class stk_classic::mesh::SymmetricTensor33
- REFACTOR Where should SymmetricTensor live, in the application, in the toolkit or a common application header?
- Member stk_classic::ParallelDatatype
- REFACTOR: Figure out a better way to typedef for non-MPI builds
- Member stk_classic::ParallelMachine
- REFACTOR: Figure out a better way to typedef for non-MPI builds
- Member stk_classic::report_deferred_messages (ParallelMachine comm)
- REFACTOR Should the message counts be broadcast to the other processors?
- Class stk_classic::StaticAssert< expression >
- REFACTOR Does StaticAssert belong here? Anywhere?
- Member stk_example_io::io_example (stk_classic::ParallelMachine comm, const std::string &in_filename, const std::string &out_filename, const std::string &decomp_method)
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_classic::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 ®ion, stk_classic::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 ®ion, stk_classic::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 ®ion, stk_classic::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 ®ion, stk_classic::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 ®ion, stk_classic::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_nodesets (Ioss::Region ®ion, stk_classic::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_output_request (Ioss::Region ®ion, stk_classic::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_classic::mesh::MetaData &meta, stk_classic::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...