Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TASK] Export of yearly cashflows #48

Open
10 tasks
Jderrill opened this issue Mar 28, 2022 · 2 comments
Open
10 tasks

[TASK] Export of yearly cashflows #48

Jderrill opened this issue Mar 28, 2022 · 2 comments
Labels
task New feature or request

Comments

@Jderrill
Copy link


Issue Description

Is your feature request related to a problem? Please describe.
It is difficult to understand the year over year cashflows or perform a discounted cashflow analysis without a proper data dump of the cashflows throughout the project lifetime.

Describe the solution you'd like
The ability to output the data for each year and each individual cashflow to a CSV file. The option to view each as discounted or not discounted would be useful as well.

Describe alternatives you've considered
I've been using the debug print out to access the cashflows, but it is difficult to extract data from the console/log file.


For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

  • 1. Is it tagged with a type: defect or task?
  • 2. Is it tagged with a priority: critical, normal or minor?
  • 3. If it will impact requirements or requirements tests, is it tagged with requirements?
  • 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
  • 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

  • 1. If the issue is a defect, is the defect fixed?
  • 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
  • 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@Jderrill Jderrill added the task New feature or request label Mar 28, 2022
@alfoa
Copy link
Collaborator

alfoa commented Nov 27, 2023

Up.

@worseliz are you guys planning to work on this capability?

@PaulTalbot-INL
Copy link
Collaborator

@alfoa what is remaining after what was done in #33 ? This allows detailed output of the cashflow analysis with period-reporting breakdowns based on using the <Output> node to request detailed outputs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants