[hk318i]

You are right, usually I check the source code to get a definitive answer. Additionally, some code testing could be needed to better understand how certain parts of OF really works.

[Asghari_M]

Originally Posted by hk318i

You are right, usually I check the source code to get a definitive answer. Additionally, some code testing could be needed to better understand how certain parts of OF really works.

Hi.
I prefer to trace/search the part of main program of OF recalling hesource at following scalarCodedSource code:

FoamFile
{
    version     2.0;
    format      ascii;
    class       dictionary;
    location    "system";
    object      fvOptions;
}
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //

energySource 
{ 
type            scalarCodedSource;
    active          true;
    selectionMode   all;
  

    scalarCodedSourceCoeffs
    {
        fieldNames      (h);
        redirectType    sourceTime;
        codeInclude
        #{

        #};

        codeCorrect
        #{
            Pout<< "**codeCorrect**" << endl;
        #};

        codeAddSup
        #{
            const Time& time = mesh().time();
            const scalarField& V = mesh_.V();
            const vectorField& C = mesh_.C();
             // How & where (which sub-program) does main program (source code) read/recall hesource?//
            scalarField& heSource = eqn.source();
            scalar hs = (2.0*time.value())/(1+time.value());
     
//   heSource +=  hs 
              .OR.
     heSource +=  hs*V;//
    Pout << "***codeAddSup***" << endl;
        #};

        codeSetValue
        #{
            Pout<< "**codeSetValue**" << endl;
        #};

        // Dummy entry. Make dependent on above to trigger recompilation
        code
        #{
            $codeInclude
            $codeCorrect
            $codeAddSup
            $codeSetValue
        #};
    }

    sourceTimeCoeffs
    {
        // Dummy entry
    }

Can u help me in how to find hesource in main program? In other words, how& where does main program use hesource as output of scalarCodedSource? How is the hesource transferred within subroutines?
I'd appreciated for any help.

[hk318i]

Tomislav Maric post about fvOptions is very good starting point to understand how fvOptions works. [LINK].

I can confirm two points here, first the source term "he" should have units of Watts [Kg m2 S-3]. Secondary the heSource should be (heSource-= hs) or (he = -hs) too act as source otherwise it will act as sink. I think that could explain the drop in Temperature in your case.

[Asghari_M]

Hello Hassan.
I conclude the correct scalarCodedSource type of fvOptions for my heat source is based on ur points as follows:

FoamFile
{
    version     2.0;
    format      ascii;
    class       dictionary;
    location    "system";
    object      fvOptions;
}
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //

energySource 
{ 
type            scalarCodedSource;
    active          true;
    selectionMode   all;
  

    scalarCodedSourceCoeffs
    {
        fieldNames      (h);
        redirectType    sourceTime;
        codeInclude
        #{

        #};

        codeCorrect
        #{
            Pout<< "**codeCorrect**" << endl;
        #};

        codeAddSup
        #{
            const Time& time = mesh().time();
            const scalarField& V = mesh_.V();
            const vectorField& C = mesh_.C();
            scalarField& heSource = eqn.source();
            scalar hs = (2.0*time.value())/(1+time.value());
     // the correct relation for hesource is presented as follows: // 
  heSource -=  hs*V;//Isn't it?//
    Pout << "***codeAddSup***" << endl;
        #};

        codeSetValue
        #{
            Pout<< "**codeSetValue**" << endl;
        #};

        // Dummy entry. Make dependent on above to trigger recompilation
        code
        #{
            $codeInclude
            $codeCorrect
            $codeAddSup
            $codeSetValue
        #};
    }

    sourceTimeCoeffs
    {
        // Dummy entry
    }

Thanks a lot for your all helpful answers during this thread.

M.Asghari

[hk318i]

Yes, it looks good. Give it a try and see the results. Please keep us updated.
Best wishes,
Hassan

[Asghari_M]

conclusion:
Really, since my heat source term is specific and scalarCodedsource returns absolute value as heSource (in watt unit), user should use *V notation (multiplying hesource by mesh volume) for scalarCodedSource type in fvOptions.
Best Wishes