Addressing the issue of #145 on kernels and postprocessors missing for RTES simulation

[wjin33]

Add kernels and postprocessors for RTES work

[moosebuild]

Job Test on c216d7c wanted to post the following:

View the site here

This comment will be updated on new commits.

[moosebuild]

Job Coverage on c216d7c wanted to post the following:

Coverage

	13ac82	#146 c216d7
	Total	Total	+/-	New
Rate	86.16%	63.34%	-22.82%	0.00%
Hits	1301	1301	-	0
Misses	209	753	+544	544

Diff coverage report

Full coverage report

Warnings

• New new line coverage rate 0.00% is less than the suggested 90.0%

This comment will be updated on new commits.

[moosebuild]

Job Coverage on c216d7c wanted to post the following:

The following coverage requirement(s) failed:

• Coverage rate 63.34% is less than the required 85.0%

[wjin33]

@moosebuild, do you know how can I revise the code so it can pass the Coverage issue?

[rpodgorney]

@wjin33 create a new branch and call it "RTES", then commit all your changes there. It should go through without needing all the coverage.

@loganharbour suggested this path forward

[wjin33]

@rpodgorney, @loganharbour, to confirm, should I create an RTES branch on my repo and merge it to the INL falcon devel branch, or should someone create a new branch called RTES in INL/falcon and merge mine to the new branch?

[rpodgorney]

The later—make a new RTES branch on idaholab/falcon —sent from my mobile device, please excuse typos or autocorrect errors Robert Podgorney, PhD, PG Directorate Fellow, Subsurface Science Energy and Environment Science and Technology Idaho National Laboratory ***@***.*** | 208-526-1524

…

________________________________ From: Wencheng Jin ***@***.***> Sent: Thursday, October 3, 2024 6:04:57 PM To: idaholab/falcon ***@***.***> Cc: Robert K. Podgorney ***@***.***>; Mention ***@***.***> Subject: Re: [idaholab/falcon] Addressing the issue of #145 on kernels and postprocessors missing for RTES simulation (PR #146) @rpodgorney<https://github.com/rpodgorney>, @loganharbour<https://github.com/loganharbour>, to confirm, should I create an RTES branch on my repo and merge it to the INL falcon devel branch, or should someone create a new branch called RTES in INL/falcon and merge mine to the new branch? — Reply to this email directly, view it on GitHub<#146 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACWGDT3X5SM2C65YA6L65SLZZXLSTAVCNFSM6AAAAABOD2G6PWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJSGUZTMMZZG4>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[wjin33]

I checked it. I am not the "admin" of this repo, so I cannot create a new branch on Idaho lab/falcon. I need someone to help.

[rpodgorney]

Let me see if I can

[rpodgorney]

@wjin33 I just created a branch called RTES—you should be able to commit your RTES code to it now