Question on declaring vector of matprops

[TheGreatCid]

Check these boxes if you have followed the posting rules.

• Q&A General is the most appropriate section for my question
• I have consulted the posting Guidelines on the Discussions front page
• I have searched the Discussions forum and my question has not been asked before
• I have searched the MOOSE website and the documentation does not answer my question
• I have formatted my post following the posting guidelines (screenshots as a last resort, triple back quotes around pasted text)

Question

Hi all,

I just want a sanity check regarding the declaration of mat props in a vector. I believe I am doing things correctly, however I am seeing a seg fault during material property declaration.

Here is a description of my method,

For the class def:

#include "Material.h"
#include "BaseNameInterface.h"
#include "MaterialProperty.h"
#include "RankTwoTensorForward.h"

class TestClass : public Material, public BaseNameInterface
public:
  static InputParameters validParams();
  TestClass(const InputParameters & parameters);
protected:
  std::vector<ADMaterialProperty<RankTwoTensor> *> _matvec;

and constructor:

TestClass::TestClass(const InputParameters & parameters):
    Material(parameters),
    BaseNameInterface(parameters)
{
  for (unsigned int i = 0; i <= 5; i++)
        _matvec[i] = &Material::declareADProperty<RankTwoTensor>("test" + std::to_string(i));
}

This is just a paired-down example, but I want to double-check that this is the correct way to do this.

Thank you!

[GiudGiud]

Hello

You need to resize the vector before accessing it at a component

Vectors are by default initialized at size 0

[GiudGiud]

also i =0 to i =5 is 6 not 5 elements

[TheGreatCid]

This example I drafted is falling apart. The issues you pointed out are not present in the actual code(of course, you could not have known that). Out-of-index issues aside, is this the correct way to initialize a vector of mat props?

[GiudGiud]

It seems fine.

Do you fill in these tensors later on? Where is the seg fault? Do you have a backtrace?

[TheGreatCid]

I figured it out. It was unrelated to how the vector was set up. The value I was using to set the size of the vec was being set to zero and I had not noticed that.