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

Losses of Energy Transfer #1823

Open
5 tasks done
NormanZielke opened this issue Mar 11, 2024 · 9 comments
Open
5 tasks done

Losses of Energy Transfer #1823

NormanZielke opened this issue Mar 11, 2024 · 9 comments
Assignees
Labels
[A] new term Including new term(s) in the ontology

Comments

@NormanZielke
Copy link
Contributor

Description of the issue

I would implement three concepts for losses of energy transfer.

  1. charging losses
  2. discharging losses
  3. self-discharging losses

Ideas of solution

Energy losses as new entity with subconcepts.
Energy losses occur due to irreversible and/or inefficient transformation processes and physical effects.
They can be caused by various mechanisms, depending on the type of energy storage device.

  1. charging losses
    Charging Losses are losses of Energy which occured by transfering energy to an energy storage.

  2. discharging losses
    Discharging Losses are losses of Energy which occured by transfering energy from an energy storage.

  3. self-discharging losses
    Self-discharge losses in energy storage refer to the inevitable energy losses that occurs when an energy storage device loses energy without transfering energy actively from it.

Workflow checklist

  • I discussed the issue with someone else than me before working on a solution
  • I already read the latest version of the workflow for this repository
  • The goal of this ontology is clear to me

I am aware that

  • every entry in the ontology should have a definition
  • classes should arise from concepts rather than from words
@NormanZielke NormanZielke added [A] new term Including new term(s) in the ontology To do Issues that haven't got discussed yet labels Mar 11, 2024
@NormanZielke NormanZielke self-assigned this Mar 11, 2024
@NormanZielke NormanZielke added this to To do in SEDOS via automation Mar 11, 2024
@github-actions github-actions bot added this to To do in Issues Mar 11, 2024
@l-emele
Copy link
Contributor

l-emele commented Mar 11, 2024

This is related to #1414.

@l-emele
Copy link
Contributor

l-emele commented Mar 18, 2024

I think, it is helpful to define a general energy loss first. Here is a first proposal: An energy loss is a process attribute that describes the difference of usable energy input and output of an energy transformation.

@NormanZielke
Copy link
Contributor Author

According to #1414 and your defintion of energy loss, i have a new approach.
Two proposals for Charging losses:

  1. Charging Losses are energy losses that describes the share of non-usable ernergy of an energy transfer
    of the input energy to an energy storage process.

Or i think a better approach could be:

  1. Charging Losses describes the difference between the input energy and the useful changing
    state of charge for an energy storage process.

@github-actions github-actions bot moved this from To do to In discussion in Issues Mar 20, 2024
@github-actions github-actions bot removed the To do Issues that haven't got discussed yet label Mar 20, 2024
@stap-m
Copy link
Contributor

stap-m commented Apr 2, 2024

I think, it is helpful to define a general energy loss first. Here is a first proposal: An energy loss is a process attribute that describes the difference of usable energy input and output of an energy transformation.

Good point.
We have waste heat in OEO: Waste thermal energy is thermal energy that is the physical output of an energy transformation process and that is released into the environment unused. We shoud somehow mention or relate it.

Further, besides energy that is not usable there might be a share of energy that might be reusable in side applications, but is not.

What about: Energy loss is a process attribute that describes the share of energy that is (unintentionally) transformed into non-usable or unused energy, e.g. waste thermal energy, during an energy transformation or transfer process.

@NormanZielke
Copy link
Contributor Author

NormanZielke commented Jun 10, 2024

What about: Energy loss is a process attribute that describes the share of energy that is (unintentionally) transformed into non-usable or unused energy, e.g. waste thermal energy, during an energy transformation or transfer process.

With @stap-m 's contribution, I have adapted my definition.

Charging Loss is an Energy loss, that describes the difference between the input energy and the useful changing
state of charge for an energy storage process during a charging process.

Discharging Loss is an Energy loss, that describes the difference between the changing
state of charge for an energy storage process and the useful output energy during a discharging process.

@l-emele
Copy link
Contributor

l-emele commented Jun 10, 2024

I thought about this again. Consider the following example:

You have 10 J of electrical energy. You charge a battery, 9 TJ are stored energy in the battery, and 1 TJ are charging losses. Then you discharge the battery, you get 8 TJ of electrical energy and 1 TJ of discharging losses. So both charging losses and are also energies. Following its definition a process attribute1 needs to be an occurent. But energy (and also energy amount value) is a continuant.

Footnotes

  1. A process attribute is a dependent occurrent that existentially depends on a process.

@areleu
Copy link
Contributor

areleu commented Jun 13, 2024

I thought about this again. Consider the following example:

You have 10 J of electrical energy. You charge a battery, 9 TJ are stored energy in the battery, and 1 TJ are charging losses. Then you discharge the battery, you get 8 TJ of electrical energy and 1 TJ of discharging losses. So both charging losses and are also energies. Following its definition a process attribute1 needs to be an occurent. But energy (and also energy amount value) is a continuant.

Footnotes

1. _A process attribute is a dependent occurrent that existentially depends on a process._ [↩](#user-content-fnref-1-d506783eb58717610ffcf34e43535d40)

I consider that process attributes should be able to refer to the quantification of different dimensions of processes. The process comprises of a net amount of "actual" energy that changes across its duration. But its magnitude can be divided in an arbitrary way depending on how it flows during the process itself. Different quantities of energy can be used to describe the same process, these can be things like losses of a battery charging or the calories burned when biking home. Both examples describe energy of some process without considering the total energy involved respectively. So I would argue that assigning it a number that refers to the attributes of particular processes should be possible and these descriptions (actual energy and quantified energy) should be able to coexist. The three would look something like this:

Process>has attribute>quantified energy(i.e. losses)>has quantity value>some value

This is one of the points that I am trying to get across in #1812 . Realized energy is differentiated from potential energy by the fact that the former can be quantified arbitrarily.

@areleu
Copy link
Contributor

areleu commented Jun 13, 2024

I think, it is helpful to define a general energy loss first. Here is a first proposal: An energy loss is a process attribute that describes the difference of usable energy input and output of an energy transformation.

I would suggest using this as an elucidation and do the description more concise and less "mathematical". Something like:

An energy loss is a process attribute that describes the amount of non-usable energy of an energy transformation.

What about: Energy loss is a process attribute that describes the share of energy that is (unintentionally) transformed into non-usable or unused energy, e.g. waste thermal energy, during an energy transformation or transfer process.

With @stap-m 's contribution, I have adapted my definition.

Charging Loss is an Energy loss, that describes the difference between the input energy and the useful changing state of charge for an energy storage process during a charging process.

Discharging Loss is an Energy loss, that describes the difference between the changing state of charge for an energy storage process and the useful output energy during a discharging process.

Same suggestion, keep the detailed explanation in the elucidation and add a concise description:

Something like Charging loss is an energy loss of a charging process.

The reason I suggest this is that, to me it seems that the more specific descriptions are prescribing the concept of losses. I mean they are constraining it to a single model:losses = input_energy - output_energy. Which is probably always true and that I suggest adding it as an elucidation. But it excludes other possible models which wouldn't surprise me that exist (When dealing with electric circuits efficiencies often have complex definitions).

@carstenhoyerklick
Copy link
Contributor

Some output of OEO-DEV 81:

  • Process attributes are occurents, energy is a continuant
    -- Energy loss (in J) cannot be a process attribute, but relative energy losses (in percent) can.
    -- There are other types of energy lost than thermal waste energy: electromagnetic radiation, chemical recombination, vibrations...
    -- Def of waste thermal energy / waste heat: Waste thermal energy is thermal energy that is the physical output of an energy transformation process and that is released into the environment unused.
  • Revisit exisiting process attributes
  • Possible definition: Energy loss is energy, that is the physical output of an energy transformation process that is not used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[A] new term Including new term(s) in the ontology
Projects
Status: In discussion
Status: To do
Issues
  
In discussion
SEDOS
  
To do
Development

No branches or pull requests

5 participants