[pooma-dev] Can no longer make new fields

[Scott Haney]

Hi John,

I just fixed a typo in Field.h. I haven't been able to reproduce your 
problem though. I can make Fields with and without CompressibleBricks 
and I call Pooma::neverCompress(). The variable initialized_s is set in 
Pooma::initialize(). Are you sure you're calling this?

Scott

On Tuesday, May 29, 2001, at 01:12 AM, John Hall wrote:

> Gang:
> I have updated to the latest POOMA and under CodeWarrior, I can no 
> longer create fields. Obviously, this is a little distressing. Here is 
> a traceback of the exception:
>
> TecFramework::MetaClass<TecFramework::IMutateTraits<poomalote::PoomaFi 
> elds, 
> poomalote::PoomaFields>>::Initialize(TecFramework::Ptr<TecFramework::A 
> nyType>) const
> TecFramework::IMutate<poomalote::PoomaFields>::Initialize(TecFramework 
> ::Ptr<TecFramework::AnyType>)
> poomalote::PoomaFields::Initialize()
> poomalote::PoomaFields::Initialize2D()
> poomalote::PoomaFields::try2D<4Vert>(const Vert&)
> poomalote::MakeField<Vert, 2, double, 2, UniformRectilinear<2, double, 
> Cartesian<2>>>::operator ()(const Vert&,const 
> std::list<TecFramework::Ptr<TecFramework::AnyType>, 
> std::allocator<TecFramework::Ptr<TecFramework::AnyType>>>&,const 
> bool&,long)
> poomalote::TecMeshD<2, UniformRectilinear<2, double, 
> Cartesian<2>>>::ExtractT<4Vert,d>(const 
> Vert&,TecFramework::Ptr<TecFramework::AnyType>)
> poomalote::TecMeshD<2, UniformRectilinear<2, double, 
> Cartesian<2>>>::getNewCenteredTypeField<4Vert,d>(const Vert&,const 
> double&)
> FieldEngineBase<2, double, CompressibleBrick>::!<Vert>(const 
> Vert&,const DomainLayout<2>&)
> Engine<2, double, CompressibleBrick>::Engine(const DomainLayout<2>&)
> CompressibleBlock<double>::CompressibleBlockController::CompressibleBl 
> ockController(int)
> Pooma::neverCompress()
> Pooma::toss_cookies(const char*,const char*,int,...)
>
> I tried to recreate the exception message that was thrown and I got:
> routine neverCompress pAssert "initialized_s" in file: "Pooma.cmpl.cpp" 
> at line 725.
>
> Any help would be appreciated.
> John Hall