Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://floss.social/users/be4foss/statuses/110536820625530320">KDE Eco (be4foss@floss.social)'s status on Wednesday, 14-Jun-2023 18:24:42 JST</a><a href="https://floss.social/@be4foss" title="be4foss@floss.social"><img src="https://gnusocial.jp/avatar/38231-48-20221124180939.webp" width="48" height="48" alt="KDE Eco" style="position: absolute; left: 0; top: 0;">KDE Eco</a><div><ul><li></ul></div></section><article><p><a href="https://floss.social/tags/FreeSoftware" rel="tag">#FreeSoftware</a> developer? Looking to measure the <a href="https://floss.social/tags/energy" rel="tag">#energy</a> consumption of your software in a dedicated lab? Can't make the trip to <a href="https://floss.social/tags/Berlin" rel="tag">#Berlin</a> to do so?</p><p>Karanjot Singh is working to change that!</p><p>This summer remote access to the <a href="https://floss.social/tags/KDAB" rel="tag">#KDAB</a> measurement lab will become a reality. Read more at the <a href="https://floss.social/tags/KDEEco" rel="tag">#KDEEco</a> blog:</p><p>"<a href="https://floss.social/tags/KEcoLab" rel="tag">#KEcoLab</a>: Remote Energy Measurement Lab"</p><p><a href="https://eco.kde.org/blog/2023-06-13-gsoc23-energy-measurement-lab/" rel="nofollow noreferrer">https://eco.kde.org/blog/2023-06-13-gsoc23-energy-measurement-lab/</a></p><p><a href="https://fosstodon.org/@drquark">@drquark</a></p><p><a href="https://floss.social/tags/KDE" rel="tag">#KDE</a> <a href="https://floss.social/tags/FEEP" rel="tag">#FEEP</a> <a href="https://floss.social/tags/BE4FOSS" rel="tag">#BE4FOSS</a> <a href="https://floss.social/tags/FOSS" rel="tag">#FOSS</a> <a href="https://floss.social/tags/OpenSource" rel="tag">#OpenSource</a> <a href="https://floss.social/tags/Sustainability" rel="tag">#Sustainability</a> <a href="https://floss.social/tags/SustainableSoftware" rel="tag">#SustainableSoftware</a> <a href="https://floss.social/tags/GreenSoftware" rel="tag">#GreenSoftware</a> <a href="https://floss.social/tags/SustainableComputing" rel="tag">#SustainableComputing</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/1652443#notice-3250883">In conversation</a><time datetime="2023-06-14T18:24:42+09:00" title="Wednesday, 14-Jun-2023 18:24:42 JST">Wednesday, 14-Jun-2023 18:24:42 JST</time> <span>from <span><a href="https://floss.social/@be4foss/110536820625530320" rel="external" title="Sent from floss.social via ActivityPub">floss.social</a></span></span><a href="https://floss.social/@be4foss/110536820625530320">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/1131248">Image showing a flow chart for remotely measuring your software's energy consumption.On the left is a drawing of a FOSS developer sitting at a laptop. The text below the images says: "Developer uploading Standard Usage Scenario on the remote portal."The first arrow in the flow chart exits rightward from the laptop and points to the Gitlab logo -- the GitLab Tanuki, which looks like an abstract raccoon dog in red and orange (designed by Ty Wilkins). Above the logo "Gitlab CI" is written. The text "SUS + Application config" is written along the arrow, indicating that the Standard Usage Scenario (SUS) and configuration file for the application being tested are uploaded to Gitlab.A second arrow exits the Gitlab logo and points to an unseen box to the far right of the image. The text "Gitlab jobs running" is written above the arrow, indicating that the energy measurement process has been started.A third arrow in the flow chart appears below the second arrow, but now it points back to the Gitlab logo. "Raw Data sent back" is written along the arrow, indicating that the energy consumption data is being sent back to Gitlab.The fourth and final arrow in the flow chart returns to the developer's computer. The text "Getting Results Back" is written along the arrow, indicating that the developer now has the results of the measurement process.Not shown in the image is the measurement lab setup at the far right of the flow chart. The full image can be seen at the blog post.</a></label><br><a href="https://cdn.masto.host/floss/media_attachments/files/110/536/808/660/780/089/original/ecdfb0cf6eb4513c.png" rel="external">https://cdn.masto.host/floss/media_attachments/files/110/536/808/660/780/089/original/ecdfb0cf6eb4513c.png</a></li><li><label><a rel="external" href="https://gnusocial.jp/attachment/1131249">Untitled attachment</a></label><br></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
KDE Eco (be4foss@floss.social)'s status on Wednesday, 14-Jun-2023 18:24:42 JSTKDE Eco
- Karan
#FreeSoftware developer? Looking to measure the #energy consumption of your software in a dedicated lab? Can't make the trip to #Berlin to do so?
Karanjot Singh is working to change that!
This summer remote access to the #KDAB measurement lab will become a reality. Read more at the #KDEEco blog:
"#KEcoLab: Remote Energy Measurement Lab"
https://eco.kde.org/blog/2023-06-13-gsoc23-energy-measurement-lab/
@drquark
#KDE #FEEP #BE4FOSS #FOSS #OpenSource #Sustainability #SustainableSoftware #GreenSoftware #SustainableComputing
In conversation2 years ago from floss.socialpermalink
Attachments
1. Image showing a flow chart for remotely measuring your software's energy consumption. On the left is a drawing of a FOSS developer sitting at a laptop. The text below the images says: "Developer uploading Standard Usage Scenario on the remote portal." The first arrow in the flow chart exits rightward from the laptop and points to the Gitlab logo -- the GitLab Tanuki, which looks like an abstract raccoon dog in red and orange (designed by Ty Wilkins). Above the logo "Gitlab CI" is written. The text "SUS + Application config" is written along the arrow, indicating that the Standard Usage Scenario (SUS) and configuration file for the application being tested are uploaded to Gitlab. A second arrow exits the Gitlab logo and points to an unseen box to the far right of the image. The text "Gitlab jobs running" is written above the arrow, indicating that the energy measurement process has been started. A third arrow in the flow chart appears below the second arrow, but now it points back to the Gitlab logo. "Raw Data sent back" is written along the arrow, indicating that the energy consumption data is being sent back to Gitlab. The fourth and final arrow in the flow chart returns to the developer's computer. The text "Getting Results Back" is written along the arrow, indicating that the developer now has the results of the measurement process. Not shown in the image is the measurement lab setup at the far right of the flow chart. The full image can be seen at the blog post.
  https://cdn.masto.host/floss/media_attachments/files/110/536/808/660/780/089/original/ecdfb0cf6eb4513c.png
2. Untitled attachment

Public

Embed Notice

HTML Code

Corresponding Notice