add export command

Codecov Report

Merging #56 (626fac0) into main (3e1847c) will decrease coverage by 0.15%.
The diff coverage is 75.87%.

@@            Coverage Diff             @@
##             main      #56      +/-   ##
==========================================
- Coverage   76.95%   76.80%   -0.14%
==========================================
  Files           9       10       +1
  Lines         720      806      +86
==========================================
+ Hits          554      619      +65
- Misses        136      150      +14
- Partials       30       37       +7

Flag
Coverage Δ

Linux
76.80% <75.87%> (-0.14%)
:arrow_down:

Windows
?

macOS
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

cmd/mail.go
62.77% <ø> (ø)

cmd/export.go
75.59% <75.59%> (ø)

cmd/delete.go
83.79% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3e1847c...626fac0. Read the comment docs.


upgrade mime & mime_guess to latest version

I realize that the future of this crate is uncertain, but can you please land this patch or another fix that updates this?
This is one of a few crates that still depends on mime_guess 1.8 which is actually broken with the experimental feature resolver -Z features.

0.17.0 published, sorry for the delay everybody.


docs: usage

Description
Usage of the async api CLI.
Related issue(s)
Fixes #810

Hey @alequetzalli, @derberg, @pratik2315, @Annysah, @starlightknown, @nelsonmic, @thulieblack this PR is ready for review.

Is this PR technically approved @derberg? 🧐 Just trying to figure out if I need to give it another TW editorial round right now or if we're waiting for you to check it again ✌🏽

@Florence-Njeri also, I noticed you have 3 PRs with new docs, and all contribute to changes in readme TOC.
I do not mind if you decide to ignore and not do these in these 3 PRs and do it in a 4th followup. Why? because if you do it in your PRs you will for sure get merge conflicts, and it is good to avoid them. Unless you never had to deal with them, so I recommend you ignore what I wrote just above, and confront merge conflicts to get experience 😄

/rtm


syst not found, findTop (check_syntax)

Issue:
./src/ecc/#jcs#fi_gd13_check_compare.prog.abap[101, 3]                   - syst not found, findTop (check_syntax)
Source:

Playground:

hmm, thought SYST was just a ddic structure, not a global variable 😄 always something new in ABAP

try again, 2.39.1

Issue resolved. Thanks.


Automated cherry pick of #1378: Fix the replicas type for the helm-chart
#1390: allow 'falsey' value in cmdOption
#1412: fix helm's default deschedulerPolicy
#1413: fix TOC location in Readme
#1416: use cmd context instead of using context.Background()
#1395: fix the issue that the pod anti-filtering rules are not

Cherry pick of #1378 #1390 #1412 #1413 #1416 #1395 on release-1.30.
#1378: Fix the replicas type for the helm-chart
#1390: allow 'falsey' value in cmdOption
#1412: fix helm's default deschedulerPolicy
#1413: fix TOC location in Readme
#1416: use cmd context instead of using context.Background()
#1395: fix the issue that the pod anti-filtering rules are not
For details on the cherry pick process, see the cherry pick requests page.

/test pull-descheduler-verify-release-1-30

/cc @ingvagabund @jklaw90

/approve
/lgtm


Add audit sink

Can you describe the purpose and include a sample use case of this?

This looks to allow someone to pass a messagehandler to intercept events? If so, I also am not sure on the purpose. One could just use another sink, correct?


[Swipeable drawer] Swap from side not working

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
I use Swipeable Drawer in a Layout component and swiping from any side in children components not working. On a button click, drawer working fine, only swiping is dead. This is due to the latest version (4.5.2).
Expected Behavior 🤔
Open drawer on swipe from side on mobile phone.
Your Environment 🌎

Tech
Version

Material-UI
v4.5.2

React
16.11.0

Browser
Chrome:  78.0.3904.87

TypeScript
3.8.0

Do you have a reproduction?

I have tested the feature on the documentation. It works as expected. We have fixed a couple of bugs (4) recently. I suspect you were benefiting from wrong behavior. Make sure no element that interferes. We can't help without a reproduction.


Refactor documentation structure for issue #1043

Pull Request Template
Description
This pull request aims to improve the structure of the Hamilton documentation, enhancing clarity and usability as the documentation grows.
Changes

Refactored the documentation structure by separating the "Integrations" section into:

Plugins: Libraries that Hamilton has extensions for.
Cookbook: Examples on how to use FastAPI with Hamilton.

How I tested this

Reviewed the modified documentation files in the docs folder to ensure that the new structure is clear and that all links and references work correctly.
Confirmed that the updated documentation renders properly without any formatting issues.

Notes

The changes address issue  #1043 regarding documentation improvements.

Checklist

[ ] PR has an informative and human-readable title (this will be pulled into the release notes)
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future TODOs are captured in comments
[ ] Project documentation has been updated if adding/changing functionality.

@skrawcz @zilto I've submitted a pull request with my changes; please review them and let me know if any adjustments are needed.

@skrawcz  Done !

@skrawcz Done !

I don't see any updates?

@Bhabuk10 we need to resolve the warnings for the build to pass - https://readthedocs.org/projects/hamilton/builds/26045579/
It seems like some TOC files can't be read.


Hacktoberfest: Fix code quality issues

Contribute to LicenseScout for the Hacktoberfest by fixing code quality issues of the project!

Sign up for Hacktoberfest to be sure that your contribution is tracked on https://hacktoberfest.digitalocean.com/profile
Check the current status of the code quality on the project's Codacy site: https://app.codacy.com/manual/aposin-bot/LicenseScout/dashboard
Identify relevant code quality issues to fix
Fix the issues and make a Pull Request (PR). If this is your first time making a PR, check the following section on the Open Source Guide from GitHub: https://opensource.guide/how-to-contribute/#opening-a-pull-request

ℹ Please, follow the quality guidelines for Hacktoberfest described in #38
Thank you and happy Hacktoberfest!

Closing as Hacktoberfest is over. Thanks to all participants!


casting .ts file

hey I want to thank you for this amazing library first.
and a quick question, do you think it may be possible to transfer directly a ts file from url load to the chromecast or i will have to edit this project for my need to transcode the ts file in golang to mp4
edit: a bit more info, i'm using streamlink to get a m3u8 file from the web and i host the feed using that same tool, it goes to <IP_ADDRESS>:any and then it waits for clients. so i can't give a link to go-cast including the extension.

I don't think chrome casts can play .ts files, here is the list of supported video formats:
https://developers.google.com/cast/docs/mpl_streaming_protocols


tests/get: add testcases with conflict scenario

Does this need to be merged after your other change?

No, it's okay to merge the change now :)


Is there a new release plan?

Hi, thanks for the package.
I need ios background download feature, which has been already merged into the master branch.
Is there any plan for next release?

Yep coming today

And released


Fix snapcast players ids

Fixes the following bug https://github.com/music-assistant/hass-music-assistant/issues/2108
The repair involves changing the player_ids so there will remain old instances of snapclients

pinging @OzGav here about the player id's that are going to change


ci: use nix-infra-bot token

I've revoked nix-infra-bot permissions on the infra repo so we can use it here for now.

We don't need them now so I've removed the token and revoked nix-infra-bot permissions for this repo.


Wrong logic in GetStyles method in RadzenDataGridColumn.razor.cs

The 'colgroup' elements are getting a width applied when resizing columns in RadzenDataGrid.  This is a problem when loading previously saved datagrid settings immediately after resizing the column.  The column width is forced to the previously resized width of the  'colgroup', and the settings width applied to the 'th' element is being overridden.
At the very top of the GetStyles method the logic is:
if (!string.IsNullOrEmpty(width) && !isForCol)

It appears there is an attempt to prevent applying width to the colgroup, however the correct logic should be like this:
if (!string.IsNullOrEmpty(width))

The problem appears to be the browser sets the manually sized width of the colgroup and nothings removes it when the settings are applied.  I tested my change and it appears to work for my use case however I don't know the reasoning of the current logic to not apply width to the colgroup.
Here is how the current method looks like for context:
public virtual string GetStyle(bool forCell = false, bool isHeaderOrFooterCell = false, bool isForCol = false)
{
    var style = new List<string>();

    var width = GetWidthOrGridSetting()?.Trim();

    if (!string.IsNullOrEmpty(width) && !isForCol)
    {
        style.Add($"width:{width}");
    }

    ...

Got it working with old code, closing.


Due to default values in configuration file you can't choose a port using own env variables.

https://github.com/adtac/commento/blob/master/config.go#L13
and then all that values are moved to env:
https://github.com/adtac/commento/blob/master/config.go#L36
So any values changed using "export" command or any other tool will be ignored.
I don't think it should work like that... why use env values at all if you can't modify them outside application?

Right, there should be a Getenv check to see if the variable is already defined. If it's not, set it. So export > .env.development.local > .env.test.local > ... > .env.
Thanks for reporing! I'll fix this.


no map widget is displied ipython 3

I installed the widget flling the readme instructions, i added the lines for off line rendering as well.
When i try to run the examples no widget is displayed. In the JS console i've this log :
https://gist.github.com/fafd6b389d99d9252470
this the lines of code is used in the notebook :
http://nbviewer.ipython.org/gist/epifanio/a96da4fde5c53755e562
my ipython version is (3, 1, 0, 'dev') running in Jupyter,  built before the big split.
python 3.4.3

Which ipython version is supposed to work with leafletwidget widget ?

I've only tested  it thoroughly with  https://github.com/ellisonbg/ipython.git commit 68f6519cdfd23581ed7358fa1941ae1bbd76e5b3

It definitely will need updating to work with ipython 3.1. @jdfreder will
know the change that need to be made...
On Thu, Apr 9, 2015 at 9:29 AM, Chris Kees<EMAIL_ADDRESS>wrote:

I've only tested it thoroughly with
https://github.com/ellisonbg/ipython.git commit
68f6519cdfd23581ed7358fa1941ae1bbd76e5b3
—
Reply to this email directly or view it on GitHub
https://github.com/ellisonbg/leafletwidget/issues/9#issuecomment-91282176
.

--
Brian E. Granger
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Probably caused by https://github.com/ipython/ipython/pull/7757 .

Any quick fix for this?

It should be fixed in leafletwidget master now, IIRC.

I'm having trouble getting this working with IPython 3.2.0, having just updated via conda update anaconda.
Specifically I'm looking at examples/DrawControl.ipynb and changed widget.ContainerWidget() to widget.Box() based on a deprecation warning, but still nothing shows up from the display(c) cell.
Three cells later the dc.last_action cell gives the error
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-11-07e2bef5fab6> in <module>()
----> 1 dc.last_action

AttributeError: 'DrawControl' object has no attribute 'last_action'

I tried the other examples an no maps show up for those either, although no exceptions are raised.

I probably won't have time to look at this for a few weeks (travel), but am
more than willing to merge a PR that fixes any of this.
On Sat, Aug 15, 2015 at 6:49 PM, Randall J. LeVeque <
<EMAIL_ADDRESS>wrote:

I'm having trouble getting this working with IPython 3.2.0, having just
updated via conda update anaconda.
Specifically I'm looking at examples/DrawControl.ipynb and changed
widget.ContainerWidget() to widget.Box() based on a deprecation warning,
but still nothing shows up from the display(c) cell.
Three cells later the dc.last_action cell gives the error

AttributeError                            Traceback (most recent call last)
 in ()
----> 1 dc.last_action
AttributeError: 'DrawControl' object has no attribute 'last_action'
I tried the other examples an no maps show up for those either, although
no exceptions are raised.
—
Reply to this email directly or view it on GitHub
https://github.com/ellisonbg/leafletwidget/issues/9#issuecomment-131474784
.

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

@willingc want to have a look at this?
On Mon, Aug 17, 2015 at 9:07 AM, Brian Granger<EMAIL_ADDRESS>wrote:

I probably won't have time to look at this for a few weeks (travel), but
am more than willing to merge a PR that fixes any of this.
On Sat, Aug 15, 2015 at 6:49 PM, Randall J. LeVeque <
<EMAIL_ADDRESS>wrote:

I'm having trouble getting this working with IPython 3.2.0, having just
updated via conda update anaconda.
Specifically I'm looking at examples/DrawControl.ipynb and changed
widget.ContainerWidget() to widget.Box() based on a deprecation warning,
but still nothing shows up from the display(c) cell.
Three cells later the dc.last_action cell gives the error

AttributeError                            Traceback (most recent call last)
 in ()
----> 1 dc.last_action
AttributeError: 'DrawControl' object has no attribute 'last_action'
I tried the other examples an no maps show up for those either, although
no exceptions are raised.
—
Reply to this email directly or view it on GitHub
https://github.com/ellisonbg/leafletwidget/issues/9#issuecomment-131474784
.

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>
--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

@ellisonbg Sure

This is "fixed" now in that the master branch works with ipywidgets 5.0.0 beta

Thanks @SylvainCorlay. Congrats on the release too.


Improve frequency abbreviation for backtrack

30m is intended to be 30 minutes, but it can just as easily be misinterpreted as 30 meters. Look into displaying 30 min or 30 minutes if no seconds are provided.

That raises a useful feature request - Backtrack interval by distance delta. If you are moving at various speeds or standing still for a while, you get a nicely spaced track. I turned on my old Garmin and I had it set to 100 feet.

That raises a useful feature request - Backtrack interval by distance delta. If you are moving at various speeds or standing still for a while, you get a nicely spaced track. I turned on my old Garmin and I had it set to 100 feet.

Thank you for the suggestion, I have created https://github.com/kylecorry31/Trail-Sense/issues/2532 to track that


Any news?

The javascript version just got a downloadable release. Is there a chance for an update to the editor?

being that the new formats are JSON, refactoring shouldn't be too hard,
but what do I know, I haven't written much code in a while.

While not impossible to update, there is functionality that is heavily dependent on particular quirks of how the old save format worked that would have to be heavily refactored, particularly around inventory management.
It is not a simple update.

Understandable. Please keep us all updated if you do go forward with a rework.

An idea could be a tool that turns the JSON save files back into the flash save files, edit the flash style files then turn them back into JSON (using the external savefile converted baked into the game). No idea if it would save time however.

I feel like the biggest hurdle to coding a save editor for the latest versions of the game would be figuring out what the flags do. Changing this current editor to be able to handle the JSON as well could be a hassle, but creating a new one is entirely possible.

figuring out what the flags do

What flags are you referring to, here?

An idea could be a tool that turns the JSON save files back into the flash save files, edit the flash style files then turn them back into JSON (using the external savefile converter baked into the game). No idea if it would save time however.

One of the things that won't quite work with a simple port is that the flash engine handled inventory slots that were empty with "empty/blank" placeholders, but the javascript one does not do so. The javascript verison also serializes all properties of the items rather than just the important bits, which would make inventory editing a nonstarter unless I built a complete inventory database with all the proper values.
In some testing I've done there might be some things I can do there, but nothing certain unless I could see how the game engine actually handles certain situations.

Why not try working with the development team to make an official Editor?
It'd probably make it a lot easier to find out what things do, and to keep it up-to-date.

Dunno if there's a way to find those flags and I'm just blind, or if it's just a case of trial and error to see what each one does.

I imagine it'd be a mix of T&E and direct correlation.
I'm not a coder by any means, so feel free to correct my assumption here, but:
Flags from F.TiTS do carry over to J.TiTS (F = Flash, J = Java), so to me it seems like old flags from F.TiTS should be easier to locate and figure out than new flags, that are exclusive to J.TiTS (Like Dizzy).
So to me it looks like it'd be easier to find out what flags do what if you correlate certain values from F.TiTS flags to flags from J.TiTS.

Okay first, Java != JavaScript. Similar name but that's where the similarities end.
Second this program is a terrible place to start a editor for the JS version of TiTs. Very few things will line up since the editing is so closely linked to the same file in it. I did consider adding a proper model system to it, but I deemed it unnecessarily complicated for the desired ends.
If I was to make an editor for the new version of TiTs, I would likely either use Java or HTML/JS for it. The reason this exists was because it was based on the original CoCEd.

Yeye, I was going to look into perhaps coding up a JS version editor myself, but the whole flags thing is annoying, hence my mention of it. I can code in HTML, CSS, JS, the only issues I'd encounter is trying to parse the JSON (mainly in terms of figuring out what parts of the file need to be changed and what each part actually means. Editing JSON is rather simple otherwise, objects ftw) and hosting the thing, though there are options for the latter.
If what Hiro said is true and that the flags do carry over, then I'd have to look at the code in this repo for what flags there are and double-check to see if they do in fact carry over (issue with that being I don't know this language and thus can't find where the parsing code is, let alone try to read it)
....Oh and I'd have to look into code for uploading and downloading the files, because I've never actually fully worked with that stuff before, at least not in this sense.

There is already atleast one being worked on https://github.com/start-5/TiTS.JS-Save-Editor

It appears that that project is dead. It has gone months without any updates or activity from the owner.

I forked that project and made a change that fixes the load error:
https://github.com/algoRhythm99/TiTS.JS-Save-Editor
I haven't tested it really though FYI :)

Chase also has his state editor (not really a save editor):
https://forum.fenoxo.com/threads/titsedjs-a-game-state-editor-for-javascript-version.32419/
I'll be closing this as Won't Fix


Split an ONNX Model

Hi,
Is it possible to use the split operation to split an ONNX Model into two models? I must basically split the LeNET DNN model into two models and run them on different machines.
Thank you in advance.

Hi,
I guess if you have a location in the graph that can easily be split (i.e., where the outputs of parent nodes can be made into the outputs of a new graph and matched to the input of the children) this should be possible… Not necessarily with the sclblonnx package thought at this point in time… We might think about adding this functionality if its sought after.

On 5 Oct 2021, at 18:02, thestarivore @.***> wrote:
Hi,
Is it possible to use the split operation to split an ONNX Model into two models? I must basically split the LeNET DNN model into two models and run them on different machines.
Thank you in advance.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/scailable/sclblonnx/issues/33, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABGHUD42ICKO46CU5ITVYWLUFMORTANCNFSM5FMBFLAA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


WebView video Url vs Video Widget performance differences

I am using Video widget to load a video from distant server. it takes some considerable time to load and at times it doesn't even open. But the same URL consistently able to load through WebView. Is it a bug.
I tried this on Scratchpad, and debug app as well. Same response differences
I am not intending to use WebView mainly because I couldn't set that autoplay. it gives a thumbnail and then someone to click to start playing.
Trying this in android6, Xiomi note

Any suggestions. I am stuck in the dilemma of using WebView  vs Widget for whole day.

Android uses the build in VideoView widget to display a video (https://developer.android.com/reference/android/widget/VideoView.html). It is also the one responsible to streaming the video url.
There is however a more feature rich external video widget from google  called ExoPlayer https://developer.android.com/guide/topics/media/exoplayer.html. This could beb wrapped in Tabris.js api to maybe yield better results.

@mpost I like the idea of using exoplayer on Android. The actual video widget is so 'basic'.

@maoamid Agreed. Would be a good third party tabris plugin.

One last question in this .. the time lag difference between open and ready event are around 10 secs.  Any idea what is controlling this? Doesn't seem to be a network / size. My video file size is 8 mb and i am in same country where i access the video, with a decent WiFi/Broadband connectivity

@natanraj Do you see a difference when bundling the video inside the app vs loading it from the network?

@mpost It is from network, not inside the app.

@natanraj Trying to narrow down the problem i was wondering if bundling VS remote loading has a performance impact.


cannot see the buttons in right side

do as the guide, I can see the button when sliding from left to right, but if I slide the cell from right to cell,I cannot see the buttons[delete, more],
is there anything more should I do?

I had this same problem. Turns out, the buttons were being displayed, but out of view. When I rotated the device (command+LeftArrow), the buttons were then visible. To fix this, I set a constraint for the trailing space to container margin on the UITableView. Hope this helps you out.


Update the Dockerfile to use the Godeps versions of libraries and to explicitly use golang:1.4

This speeds up the build (and makes it more consistent) since it doesn't have to clone a bunch of repos. :+1:
With this change, my final image is ~493.8 MB (versus ~567.7 MB when I build from master).
Also:
$ time docker build --no-cache .
...
real	0m38.081s
user	0m0.027s
sys	0m0.029s

Versus:
$ time docker build --no-cache https://github.com/docker/distribution.git
...
real	1m31.629s
user	0m0.145s
sys	0m0.082s

(most of which is spent in Step 2 : RUN go get github.com/docker/distribution/...)

@tianon Thanks for doing this.
Unfortunately, before we merge this, we need to update the circle.yml file to build with godep.

With #98, we can safely merge this now.


Add Initial Java Support for GDS to KvikIO

This PR is intended to add initial support for Java binding to GDS as part of the KvikIO library. In this PR are the minimal set of bindings required to support synchronous read and write IO operations via GDS as well as a single example to demonstrate how the bindings can be used alongside other CUDA libraries, such as JCuda. Full support for the GDS CuFile API, including batch and asynchronous IO, has not yet been implemented and more sophisticated error/exception handling is not yet in place. There is a README located within kvikio/java detailing how this new functionality can be compiled and built locally, along with detailed instructions on how to run the included usage example.

/ok to test

/ok to test

Is this still planned for 24.08 or should we move to 24.10?

I will not likely finish the updates here for a couple weeks due to other priorities, so this should be moved to 24.10

Ok thanks Alex! 🙏
Have moved to 24.10

Quick first pass of review -- mostly focused on packaging and CI. Give my suggestions a try and I'll comment /ok to test to run your next commits on CI.

@bdice I believe I have updated the PR with all of your suggestions, except for the versioning question you had. Please let me know if you had further thoughts there or if it seems that I missed anything!

/ok to test

/ok to test

/ok to test

@madsbk or @bdice would one of you be able to try and run this through the build tests? I have updated it to try and make it more agnostic to the build location. It works on my machine, but need to know if there are more build errors remaining to be fixed for the CI/CD machines.

/ok to test

/ok to test

/ok to test

@aslobodaNV Looks like there are CI build failures. I'm not sure how to diagnose this.
Error:  Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project cufile: Fatal error compiling: error: invalid target release: 21 -> [Help 1]

/ok to test

/ok to test

/ok to test

@aslobodaNV Great work. I left some comments but we should be able to get this merged after they are addressed.

@madsbk Do you want to target 24.12 or 25.02?

I have no strong opinion but it might make sense to add some more features before we release?
@aslobodaNV do you want this to part of the 24.12 release? Or should we have it in the nightly channel until 25.02?

@aslobodaNV Great work. I left some comments but we should be able to get this merged after they are addressed.

@bdice Addressed all comments except the rapids url change. Please confirm that it should differ from the one used in the cudf repo.

One last CI run, then this should be good to go.

/ok to test

/merge

/ok to test

/ok to test

/merge


Dapr Pub/Sub improvements

Issue Description
Dapr will only call the /dapr/subscribe route once to discover which topic subscriptions we are listening on.
Next to that, we internally utilize a WebServerSingleton that takes care of the internal webserver. This will be initialized and start listening on its port as soon as the getServer() method is awaited once.
Tasks
To ensure that we allow Dapr to correctly subscribe the topics, we should thus do:

[ ] Allow the user to register routes (without calling the getServer() method since this will start listening and Dapr will initialize)
[ ] Allow the user to initialize the client library after registering the routes, which should start the server to listen.

(Thanks for reporting @Amenocy)
Reference
https://docs.dapr.io/developing-applications/building-blocks/pubsub/howto-publish-subscribe/#programmatic-subscriptions
https://docs.dapr.io/reference/api/pubsub_api/

https://github.com/Roadwork/dapr-js-sdk/commit/6aca7807fe2683d650b5796d14a9c094f281a3fe


Remove ! (not) from if statement

Removing the ! from the if statement to align the code functionality with the description if the behavior in the comment

@ggailey777

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks @mmckechney for this fix, which seems correct to me. Because I didn't write this code, we need to get @davidmrdavid to double-check your fix.
#assign:davidmrdavid

LGTM @ggailey777. Thanks @mmckechney for your contribution :)


Plot space that crosses 180 degrees

Below is my attempt to plot SST in the Pacific Ocean between 5S and 5N, and between 160W and 80E.

As you can see, it is plotted from 180E to 180W instead of breaking the plot in the region where there is no data. This causes additional problems because if I try to set the x limits from 160 to -80 in any fashion (i.e. adding 360 to the second number or subtracting from the first), the plot focuses on the region with no data.
If someone could quickly explain to me how to change the longitude breakingpoint of the plot, I'd be much appreciative. I cannot come up with useful search words.
https://github.com/SciTools/iris/blob/2a9e131875be42c39ab4b8fc9956e4a4d59f83a2/lib/iris/quickplot.py#L4

@SciTools/peloton There are a number of potential causes for the graph not working as expected, to pinpoint the problem we would need to recreate the cube or have access to the data. Could you upload a single timestep of the cube?
Thanks for raising this!

pacific_example.zip
Thank you!

Can replicate the issue in the latest iris version.
import iris
import iris.quickplot as qplt

cube = iris.load_cube("pacific_example.nc")
qplt.pcolormesh(cube)

If I plot the data manually using a PlateCarree projection I get a contiguous plot as expected
import matplotlib.pyplot as plt
import cartopy.crs as ccrs

ax = plt.axes(projection=ccrs.PlateCarree())
plt.pcolormesh(cube.data,transform=ccrs.PlateCarree())

And the cube doesn't have any coord_system attached so it should be using PlateCarree
print(cube.coord_system())
None
print(cube.coord("latitude").coord_system
None
print(cube.coord("longitude").coord_system
None

That's my initial ideas, any other thoughts on the cause of this issue?

Update:
Though I have not changed my code at all, the effect of setting the limits of the plot has changed:
Now if I set the limits to [160-360, -80] it will show me [-180,-80];
and if I set the limits to [160, 360-80], it will show me [160,180],
but the only way to see both at the same time is to not limit the x-axis, in which case the figure still spans from -180 to 180 with a large section of no data in the middle, as before.
(setting the limits to [160, -80] still shows just the area with no data)
Any further thoughts in the meantime on how to deal with this issue @HGWright?

I think you need to set up your GeoAxes with a chosen central longitude (default is 0).
import matplotlib.pyplot as plt
import cartopy.crs as ccrs
import iris
import iris.quickplot as qplt

cube = iris.load_cube("pacific_example.nc")
ax = plt.subplot(111, projection=ccrs.PlateCarree(central_longitude=210))
qplt.pcolormesh(cube, axes=ax)
plt.show()

Arguable Iris could/should be more clever about choosing that for you automatically.

@SciTools/peloton Do you need further assistance @rebeccaherman1 with this issue?

Maybe have a look at Cartopy's gridlines method for axis labels.  xticks is a Matplotlib thing, and Matplotlib doesn't know anything about Cartopy's special transforms.
import matplotlib.pyplot as plt
import cartopy.crs as ccrs
import numpy as np
import iris
import iris.quickplot as qplt

cube = iris.load_cube("pacific_example.nc")
ax = plt.axes(projection=ccrs.PlateCarree(central_longitude=210))
qplt.pcolormesh(cube, axes=ax)

ax.gridlines(draw_labels=True, linewidth=0, xlocs=[160, 180, -160, -140, -120, -100, -80])

plt.show()

Thank you, that is helpful.
I must say that I find the available functions somewhat frustrating. I don't like that gridlines() labels 4.5N and S rather than 5N and S, which mark the top and bottom of the plot. If I try to include these ticks forcibly, qplt elongates the plot to include up to 8N and S with no data there. Something similar happens when I try to use set_extent instead of the matplotlib xlims. Any ideas on how to avoid this?
For another plot, I believe I need to use set_extent because for some reason the plot fills in all the missing space with the color of the last point, and it also adds white space at the top.
Without set_extent:

With set_extent:

I'm not sure about the set_extent behaviour, but set_ylim seems to work as expected for me.  If you look at the bounds of your latitude coordinate, they only extend to +/- 4.71 degrees, so that will determine the default axis limits.
For your EOF plot, the most likely explanation is that the circular property of your longitude coordinate is set to True when it should be False.

Thanks for the explanation and the idea, @rcomer.

I'm not sure about the set_extent behaviour, but set_ylim seems to work as expected for me. If you look at the bounds of your latitude coordinate, they only extend to +/- 4.71 degrees, so that will determine the default axis limits.

I think I wasn't expecting this because I had called extract_region using [-5,5]. Would the bounds be lower because of the grid? Or because they mark the center of the grid point rather than the edge?

For your EOF plot, the most likely explanation is that the circular property of your longitude coordinate is set to True when it should be False.

This is a property of the cube itself, right? It was a good idea, but I have checked, and the circular property of all components is set to 0. Incidentally, I wondered if this was potentially a reason why I was having trouble plotting the pacific_example, and if setting the coordinates to circular could stand in for setting the center of the plot. However, this does not help.

@SciTools/peloton We are converting to a discussion as it seems to have moved on from the original question.


FancyZones stops working

Microsoft PowerToys version
0.41.4
Running as admin

[X] Yes

Area(s) with issue?
FancyZones, FancyZones Editor
Steps to reproduce
When using FancyZones I always move windows pressing the secondary mouse button. After a while it just stops working and I must disable/reenable FancyZones in the Settings menu. After a while disabling/reenabling doesn't fix it anymore and it just stops working all together.
Even the editor doesn't open anymore.
PowerToysReport_2021-07-21-11-54-27.zip
✔ Expected Behavior
When dragging Windows and pressing the secondary mouse button the zones should show and the window would resize to fit the selected zone.
❌ Actual Behavior
When dragging Windows and pressing the secondary mouse button the zones don't appear and nothing works.
Other Software
Google Chrome (the one I usually put in zones)
TS Plus (remote desktop application, this one doesn't respond to zones and can't be resized - could it be the culprid?)

@diegocjorge would you be able to install a private unsigned build to help us troubleshoot the issue? In this build I added logs to localize the problem.

Uninstall PowerToys
Install https://github.com/SeraphimaZ/PowerToys/blob/crash_logs/private_build/PowerToysSetup-0.0.1-x64.exe
Upload the bug report after the issue is reproduced

Thank you for your help!

I have been using the unsigned build for the past 6 days, but the issue never manifested.
In this build the TSPlus application started responding to the zones (they will turn blue), but the window will not resize.

In this build the TSPlus application started responding to the zones (they will turn blue), but the window will not resize.

Could you please create another issue for this problem? It's not related to the issue described here. I would appreciate screenshots and steps to reproduce the bug. Thanks!

@SeraphimaZ sounds like this was fixed in the unsigned build, was the fix here checked in?

@crutkas in the unsigned build I just added logs to localize the problem. Looks like during installation some files weren't updated and full uninstalling and reinstalling solved the problem.

@diegocjorge can you please verify if the problem is reproducible in the latest PowerToys version? Thanks!

@SeraphimaZ the bug that caused FancyZones to stop working seems fixed.
The TSPlus windows still don't resize when I put them in a zone. Since TSPlus is an RDP application it's probably due to way it's coded or how it manages its windows. It's not a big deal that it doesn't work, all other apps work simply fine.
Thanks for all the help and, most importantly, for developing this awesome tool. It makes my daily use of Windows much more enjoyable :)


🐛 Slider cannot be moved sometimes

Describe the bug
Sometimes when the slider knob is at one of the slider bar's ends it cannot be moved anymore. As you can see from the screenshot, on hovering the knob, it reacts at first but then appears to be "unhovered" - although the mouse pointer is still on top of the knob. The knob cannot be moved by dragging then.

To Reproduce

Go to fluent_ui showcase and move the slider to one of the very ends of the bar.
Move the mouse pointer over the knob a couple of times. It may take some tries but sooner or late it won't react in the expected way.

I started work on it, sounds good for me.

Can you still reproduce this issue on the latest version?

Using v4.8.7 I cannot reproduce this issue anymore apparently.

Thanks. It was fixed by #1046


[feature] - Create validation middleware and initial validation rules

Description
Create an express middleware for validation of all input data to API endpoints using the hapi/joi validation package. Create a directory (or a file if not too large) containing various validation rules for existing models (note: more rules will be added over time).
Resources
https://dev.to/jacqueline/using-hapi-joi-version-16-1-7-to-validate-a-request-body-in-a-restful-api-bje
Acceptance Criteria

[ ] 1. Create validation middleware capable of receiving input
[ ] 2. Create validation rules in a central location, at least for /api/v1/auth/reporter endpoints

We can create a folder for every validation needed, and we need to know the fields that need to be validated, how are we going to set that

Sorry @ifeLight this message was lost in a ton of mail I got yesterday. The existing models will be a good place to start


Add Sumologic returners && fixed Graylog returner bug

Hello!
I've tested these Sumologic returners and validated they all work. Also while putting these together, I noticed a bug in the graylog returners (graylog_nebula_return.py and graylog_nova_return.py) that was created likely with a find/replace that went wrong.
Thanks!

CLA is signed now. thx!

Awesome! Thanks for jumping through that extra hoop for us. Legal, amirite? ;)


Change source distribution format from deprecated zip to tag.gz

Python source distribution format has been standardized to tag.gz by PEP 625. We currently use zip  and PyPI has recently started sending deprecation warnings about that. Best to change the format before its support is removed altogether. In addition to change package itself, we need to make sure installation instructions are updated.
This change doesn't affect normal users because pip install robotframework uses the wheel distribution and even when installing a downloaded source distribution, pip handles both formats fine. The change affects only users who download the source distribution and extract it, but that kind of usage is likely pretty rare. Those who actually want to see the source, typically clone the repository instead. Anyway, the change is somewhat backwards incompatible and needs to be mentioned in the release notes.

Notice that the format used to be tar.gz, but we changed it to zip in RF 3.1 to make opening the source distribution easier on Windows. One reason was that there were installation problems that required extracting the package. We don't have such issues anymore, so there shouldn't be needs to open it too often.


FAST.Farm

Hello everyone, I'm trying to run a simulation in FAST.Farm using the NREL5MW wind turbine, but the following error occured:
Farm_Initialize:InflowWind_CalcOutput:CalcOutput:IfW_FFWind_CalcOutput [position=(4980, 4980,
345)  in wind-file coordinates]: Error: FF wind array was exhausted at 2 seconds (trying to
access data at -406.96 seconds).
Aborting FAST.Farm.
How can I fix it? Thanks a lot!

Dear @Tommi1198,
Have you generated your turbulent wind data file using TurbSim following the modeling guidance documentation: https://openfast.readthedocs.io/en/main/source/user/fast.farm/ModelGuidance.html#inflow-wind-generation?  Is the turbulent wind data periodic as recommended?  I would not expect that you'd receive an error regarding

FF wind array was exhausted

if the wind data is periodic.
Best regards,

Dear @Tommi1198,
I don't see any issue with this InflowWind input file.  The issue is likely with the TurbSim wind data file you are using, 90m_12mps_twr.bts.
How did you generate this file from TurbSim and is it periodic, i.e., is TurbSim input UsableTime set to "ALL"?
Best regards,

Dear @jjonkman, I took this file from the library in GitHub; in addition, I donìt know how to open this file so that I can check if TurbSim input UsableTime set to "ALL". What can I do? Thank you

Dear @Tommi1198,
Presumably you obtained the file 90m_12mps_twr.bts from here: https://github.com/OpenFAST/r-test/tree/main/glue-codes/openfast/5MW_Baseline/Wind; is that correct?  The TurbSim input file used to generate this wind data file is available in the same directory, 90m_12mps_twr.inp.  In this file, UsableTime is set to 60 s, not "ALL".  And there are other input parameters in this TurbSim input file that also do not follow the modeling guidance for TurbSim specified in the FAST.Farm documentation.
The TurbSim input file, 90m_08_mps.inp, found in the following example more closely follows the modeling guidance for TurbSim specified in the FAST.Farm documentation: https://github.com/OpenFAST/r-test/tree/main/glue-codes/fast-farm/TSinflow.  I would start with this example.
Best regards,

Dear @jjonkman, I changed the wind file using 90m_08_mps.bts as bts file for TurbSim, but another error came out:
Farm_Initialize:InflowWind_CalcOutput:CalcOutput:IfW_FFWind_CalcOutput [position=(4980, 4980,
345)  in wind-file coordinates]: FF wind array boundaries violated: Grid too small in Y
direction. Y=4980; Y boundaries = [-500, 500]
Aborting FAST.Farm.
How can I change the Y boundaries?
This is my input file for the wind:
------- InflowWind INPUT FILE -------------------------------------------------------------------------
12 m/s turbulent winds on 31x31 FF grid and tower for FAST CertTests #18, #19, #21, #22, #23, and #24
False         Echo           - Echo input data to .ech (flag)
3   WindType       - switch for wind file type (1=steady; 2=uniform; 3=binary TurbSim FF; 4=binary Bladed-style FF; 5=HAWC format; 6=User defined; 7=native Bladed FF)
0   PropagationDir - Direction of wind propagation (meteorological rotation from aligned with X (positive rotates towards -Y) -- degrees) (not used for native Bladed format WindType=7)
0   VFlowAng       - Upflow angle (degrees) (not used for native Bladed format WindType=7)
1   NWindVel       - Number of points to output the wind velocity    (0 to 9)
0   WindVxiList    - List of coordinates in the inertial X direction (m)
0   WindVyiList    - List of coordinates in the inertial Y direction (m)
90   WindVziList    - List of coordinates in the inertial Z direction (m)
================== Parameters for Steady Wind Conditions [used only for WindType = 1] =========================
15   HWindSpeed     - Horizontal wind speed                           (m/s)
90   RefHt          - Reference height for horizontal wind speed      (m)
0.2   PLExp          - Power law exponent                              (-)
================== Parameters for Uniform wind file   [used only for WindType = 2] ============================
"unused"      Filename_Uni   - Filename of time series data for uniform wind field.      (-)
90   RefHt_Uni      - Reference height for horizontal wind speed                (m)
125.88   RefLength      - Reference length for linear horizontal and vertical sheer (-)
================== Parameters for Binary TurbSim Full-Field files   [used only for WindType = 3] ==============
"90m_08mps.bts"    FileName_BTS   - Name of the Full field wind file to use (.bts)
================== Parameters for Binary Bladed-style Full-Field files   [used only for WindType = 4 or WindType = 7] =========
"unused"      FileNameRoot   - WindType=4: Rootname of the full-field wind file to use (.wnd, .sum); WindType=7: name of the intermediate file with wind scaling values
False         TowerFile      - Have tower file (.twr) (flag) ignored when WindType = 7
================== Parameters for HAWC-format binary files  [Only used with WindType = 5] =====================
"wasp\Output\basic_5u.bin"    FileName_u     - name of the file containing the u-component fluctuating wind (.bin)
"wasp\Output\basic_5v.bin"    FileName_v     - name of the file containing the v-component fluctuating wind (.bin)
"wasp\Output\basic_5w.bin"    FileName_w     - name of the file containing the w-component fluctuating wind (.bin)
64   nx             - number of grids in the x direction (in the 3 files above) (-)
32   ny             - number of grids in the y direction (in the 3 files above) (-)
32   nz             - number of grids in the z direction (in the 3 files above) (-)
16   dx             - distance (in meters) between points in the x direction    (m)
3   dy             - distance (in meters) between points in the y direction    (m)
3   dz             - distance (in meters) between points in the z direction    (m)
90   RefHt_Hawc     - reference height; the height (in meters) of the vertical center of the grid (m)
-------------   Scaling parameters for turbulence   ---------------------------------------------------------
2   ScaleMethod    - Turbulence scaling method   [0 = none, 1 = direct scaling, 2 = calculate scaling factor based on a desired standard deviation]
1   SFx            - Turbulence scaling factor for the x direction (-)   [ScaleMethod=1]
1   SFy            - Turbulence scaling factor for the y direction (-)   [ScaleMethod=1]
1   SFz            - Turbulence scaling factor for the z direction (-)   [ScaleMethod=1]
1.2   SigmaFx        - Turbulence standard deviation to calculate scaling from in x direction (m/s)    [ScaleMethod=2]
0.8   SigmaFy        - Turbulence standard deviation to calculate scaling from in y direction (m/s)    [ScaleMethod=2]
0.2   SigmaFz        - Turbulence standard deviation to calculate scaling from in z direction (m/s)    [ScaleMethod=2]
-------------   Mean wind profile parameters (added to HAWC-format files)   ---------------------------------
12   URef           - Mean u-component wind speed at the reference height (m/s)
2   WindProfile    - Wind profile type (0=constant;1=logarithmic,2=power law)
0.2   PLExp_Hawc     - Power law exponent (-) (used for PL wind profile type only)
0.03   Z0             - Surface roughness length (m) (used for LG wind profile type only)
0   XOffset         - Initial offset in +x direction (shift of wind box)
====================== OUTPUT ==================================================
False         SumPrint     - Print summary data to .IfW.sum (flag)
OutList      - The next line(s) contains a list of output parameters.  See OutListParameters.xlsx for a listing of available output channels, (-)
"Wind1VelX"               X-direction wind velocity at point WindList(1)
"Wind1VelY"               Y-direction wind velocity at point WindList(1)
"Wind1VelZ"               Z-direction wind velocity at point WindList(1)
END of input file (the word "END" must appear in the first 3 columns of this last OutList line)

@Tommi1198
Your turbine is too far out of the bounds of the wind field.  About 5 km away from the center based on [position=(4980, 4980, 345).  Is that the correct position for the turbine?

Dear @andrew-platt, my turbine is in this position:
WT_X    WT_Y     WT_Z
(m)     (m)      (m)
100.0  180.0    0.0

This is a bit puzzling.  What is asking for wind 5 km away at position=(4980, 4980, 345)?

I don't really know...

Dear @Tommi1198,
My guess is your low- or high-resolution domains defined in your FAST.Farm input file have points that are outside the domain of your TurbSim wind data file.
Best regards,

Dear @jjonkman, how can I see if I have some points outside the TurbSim domain? Because I tried to extend the resolution of the turbine but nothing changed

Dear @Tommi1198,
You specify the X-Y-Z extent of the low- and high-resolution domains used by FAST.Farm in the FAST.Farm input file.  And you specify the Y-Z extent of the TurbSim domain(s) used by the InflowWind module of FAST.Farm in the TurbSim input file (due to its periodicity, the X-extent of the TurbSim domain is infinite when UsableTime = "ALL").  The low- and high-resolution domains of FAST.Farm must lie within the TurbSim domain (and preferably align with the TurbSim domain to avoid extra interpolation) as discussed in the Modeling Guidance section of the online FAST.Farm documentation: https://openfast.readthedocs.io/en/main/source/user/fast.farm/ModelGuidance.html.
Best regards,

Dear @jjonkman, I have no idea how to open the .bts file to change the domain of the TurbSim input file...I tried to open it with a program found on the internet, but it didn't work

Dear @Tommi1198,
You shouldn't edit the binary wind data file manually.  The TurbSim domain (and other wind conditions) is specified in the TurbSim input file.  The TurbSim output file can then be generated by rerunning TurbSim.
Best regards,

Dear @jjonkman, the following error continued to show:
Farm_Initialize:InflowWind_CalcOutput:CalcOutput:IfW_FFWind_CalcOutput [position=(4975, 9950,
340)  in wind-file coordinates]: FF wind array boundaries violated: Grid too small in Y
direction. Y=9950; Y boundaries = [-500, 500]
Aborting FAST.Farm.
So, I enlarged the grid in Y direction and the following error came out:
forrtl: severe (157): Program Exception - access violationiod of 200 seconds).
Image              PC                Routine            Line        Source
FAST.Farm_x64.exe  00007FF7A16BBF97  Unknown               Unknown  Unknown
FAST.Farm_x64.exe  00007FF7A16B9F2B  Unknown               Unknown  Unknown
FAST.Farm_x64.exe  00007FF7A169E7ED  Unknown               Unknown  Unknown
FAST.Farm_x64.exe  00007FF7A0A2C0C5  Unknown               Unknown  Unknown
FAST.Farm_x64.exe  00007FF7A070C725  Unknown               Unknown  Unknown
FAST.Farm_x64.exe  00007FF7A08E3521  Unknown               Unknown  Unknown
FAST.Farm_x64.exe  00007FF7A08CCEAE  Unknown               Unknown  Unknown
FAST.Farm_x64.exe  00007FF7A07013EE  Unknown               Unknown  Unknown
FAST.Farm_x64.exe  00007FF7A2F23B62  Unknown               Unknown  Unknown
FAST.Farm_x64.exe  00007FF7A341F934  Unknown               Unknown  Unknown
KERNEL32.DLL       00007FF9D2E754E0  Unknown               Unknown  Unknown
ntdll.dll          00007FF9D3A6485B  Unknown               Unknown  Unknown
What can I do? Thanks a lot!

Dear @Tommi1198,
Can you clarify what you mean when you say that you "enlarged the grid in Y direction"?
Best regards,

Dear @jjonkman, I mean that, when I had the first error, I read on the guide that the problem was regarding the low-resolution domain, so I enlarged it; then, the second error described above came out

Dear @Tommi1198,
Can you share your FAST.Farm input file, InflowWind input file, and TurbSim input file?
Best regards,

Input file.zip
Dear @jjonkman, here what you asked for, thanks a lot!

Dear @Tommi1198,
I'm still not sure what is resulting in the access violation error, but perhaps that is the same issue discussed previously: https://github.com/OpenFAST/openfast/issues/1044?
Regardless, I still see that you are not setting up your FAST.Farm discretizations correctly.  Just a few comments:

The low-resolution domain is skewed way to one side in Y and the dY_Low spacing is large.
The dr spacing of the wake planes (radial finite-difference grid) is way to large.

Can you explain why you are setting up your model this way?
By now, you've asked a series of FAST.Farm questions, but you have not followed our recommendations, i.e., to set up your model following the documented modeling guidance and provided Python scripts.  I'm not sure how to help if you don't follow our recommendations.
Best regards,

@jjonkman @Tommi1198 @andrew-platt @sayerhs @itd
respected sir,sir i am a student  and doing my academic project on OWT but i can't understand,how to use this software,
how to download it ?
is matlab necessary to run this software?
i seek your atteention for help.
as a new member ,kindly help me so that i can contribute in this in future.

@jyotrimaya1993,
I recommend starting with the documentation here: https://openfast.readthedocs.io/en/main/index.html

@jyotrimaya1993,
I recommend starting with the documentation here: https://openfast.readthedocs.io/en/main/index.html

sir, this installation process is old,and after following also i am unable to install the software

Dear @jyotrimaya1993,
What is your operating system, which approach from the documentation are you trying to use to install OpenFAST, and which step in the process is not working for you?
Best regards,

sir, windows os
in step 1 -i download visual studio community 2019
step 2 -i download fortran compiler with math library
step 3- i download the zip file from openFAST git hub
step 4 -i download all the assets except that 2 last  source code zip file
step 5-unzip all the downloaded file
step 6-while running in powershell through the  .exe code following that fst file...
it is not running....
it only show that path only

Dear @jyotrimaya1993,
In Windows, the precompiled binary executables have been provided.   So, unless you intend to modify the source code, requiring a recompile, you can likely skip steps 1-3.
To run the precompiled OpenFAST executable from a Windows command prompt, see, e.g., https://github.com/OpenFAST/openfast/issues/463.
Best regards,

what should i do now?
this thingh i got error

OpenFAST
Copyright (C) 2022 National Renewable Energy Laboratory
Copyright (C) 2022 Envision Energy USA LTD
This program is licensed under Apache License Version 2.0 and comes with ABSOLUTELY NO WARRANTY.
See the "LICENSE" file distributed with this software for details.

OpenFAST-v3.1.0
Compile Info:

Compiler: Intel(R) Fortran Compiler 1900
Architecture: 64 bit
Precision: single
OpenMP: No
Date: Mar 08 2022
Time: 10:53:02
Execution Info:
Date: 05/05/2022
Time: 01:01:46+0530

OpenFAST input file heading:
FAST Certification Test #22: NREL 5.0 MW Baseline Wind Turbine with ITI Barge Configuration,
for use in offshore analysis
Running ElastoDyn.
Nodal outputs section of ElastoDyn input file not found or improperly formatted.
Running AeroDyn14.
WARNING:   AeroDyn 14 is deprecated and will be removed in a future release.
Running InflowWind.
Reading a 31x31 grid (145 m wide, 17.5 m to 162.5 m above ground) with a characteristic wind
speed of 12 m/s. This full-field file was generated by TurbSim (v1.06.00, 21-Sep-2012) on
07-Jan-2014 at 12:50:45.
Processed 1442 time steps of 20-Hz full-field data (72.05 seconds).
Running HydroDyn.
Generating incident wave kinematics and current time history.
Reading in WAMIT output with root name ".../5MW_Baseline/HydroData/Barge".
Computing radiation impulse response functions and wave diffraction forces.
Using SS_Radiation Module, with 30 of 30 radiation states
MAP++ environment properties (set externally)...
Gravity constant          [m/s^2]  : 9.81
Sea density               [kg/m^3] : 1025.00
Water depth               [m]      : 150.00
Vessel reference position [m]      : 0.00 , 0.00 , 0.00
Running ServoDyn.
Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ).
FAST_InitializeAll:SrvD_Init:BladedInterface_Init:The dynamic library
.../5MW_Baseline/ServoData/DISCON_ITIBarge.dll could not be loaded. Check that the file exists
in the specified location and that it is compiled for 64-bit applications.
OpenFAST encountered an error during module initialization.
Simulation error level: FATAL ERROR
Aborting OpenFAST.

Dear @jyotrimaya1993,
See a similar question asked and answered here: https://github.com/OpenFAST/openfast/discussions/1114.
Best regards

@rafmudaf kindly guide me to solve  my issue

Dear @jyotrimaya1993,
You received the message "OpenFAST terminated normally".  So, there is no issue to be solved.
The warning about the deprecation of AeroDyn v14 is suggesting that you consider upgrading from AeroDyn v14 (CompAero = 1) to AeroDyn v15 (CompAero = 2) because we intend to eliminate AeroDyn v14 from OpenFAST in a future release (expected to happen soon).  I'm not sure if you've modified the r-test input files in any way, but when we deprecate AeroDyn v14, we will upgrade all of the r-test cases that use AeroDyn v14 to use AeroDyn v15.
Best regards,

@jjonkman thank you sir,for your co-operation ,being new to this ,somehow i feel difficulty in installing ,but due to your help ,successfully i installed it ,Hopefully in near future you may help me in same manner

@jjonkman i am not getting the vtk files folder in my reg glue code. and this type of error is coming..
OpenFAST-v3.1.0
Compile Info:

Compiler: Intel(R) Fortran Compiler 1900
Architecture: 64 bit
Precision: single
OpenMP: No
Date: Mar 08 2022
Time: 10:53:02
Execution Info:
Date: 05/07/2022
Time: 13:42:59+0530

OpenFAST input file heading:
FAST Certification Test #25: NREL 5.0 MW Baseline Wind Turbine with OC4-DeepCwind semi
configuration, for use in offshore analysis
FAST_InitializeAll:FAST_Init:FAST_ReadPrimaryFile:1/VTK_fps is not an integer multiple of DT.
FAST will output VTK information at 16 fps, the closest rate possible.
FAST_Init:ValidateInputData:Tmax is less than the last linearization time. Linearization analysis
will not be performed after TMax.
ValidateInputData:Linearization is not implemented for the OpenFOAM coupling.
ValidateInputData:Linearization is not implemented for the FEAMooring or MoorDyn mooring modules.
ValidateInputData:DT_out must be an integer multiple of DT.
OpenFAST encountered an error during module initialization.
Simulation error level: FATAL ERROR
Aborting OpenFAST.
PS C:\openfast\r-test-061441958a2eef7f494d69ee097f8ec050d5a129\r-test-061441958a2eef7f494d69ee097f8ec050d5a129\glue-codes\openfast\5MW_OC4Semi_Linear>

Dear @jyotrimaya1993,
It appears that your OpenFAST model has several errors that that need to be resolved before you can run the simulation.  These are the errors reported that are preventing the simulation from running:
ValidateInputData:Linearization is not implemented for the OpenFOAM coupling.
<-- To solve this error, either disable linearization (Linearize = False) or use InflowWind instead of OpenFOAM (CompInflow = 1).
ValidateInputData:Linearization is not implemented for the FEAMooring or MoorDyn mooring modules.
<-- To solve this error, either disable linearization (Linearize = False) or use MAP++ instead of FEAMooring or MoorDyn (CompMooring = 1).
ValidateInputData:DT_out must be an integer multiple of DT.
<-- To solve this error, set DT_Out to be an integer multiple of DT.
Best regards,

Dear @jjonkman ,
I am facing a similar problem while running the FAST.Farm_x64_OMP.exe.
I got the following info and the software just stop running, could you please specify how shall I solve this?
.......
Running ServoDyn.
Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ).
Using legacy Bladed DLL interface.
FAST_InitializeAll:FAST_Init:FAST_ReadPrimaryFile:1/VTK_fps is not an integer multiple of DT.
FAST will output VTK information at 14.545 fps, the closest rate possible.
It didn't show 'aborting ...' but it seemed just stop running and no outb file was generated.
Thank you in advance.
Yours sincerely,
Yuan

Dear @yuangao0916,
The warning about VTK_fps is just a warning, it will not cause the simulation to abort.
Can you share the full output from the Windows command prompt when you attempt to run FAST.Farm?
Best regards,

@jjonkman  why it is showing "Nodal outputs section of ElastoDyn input file not found or improperly formatted."(below result)

OpenFAST
Copyright (C) 2022 National Renewable Energy Laboratory
Copyright (C) 2022 Envision Energy USA LTD
This program is licensed under Apache License Version 2.0 and comes with ABSOLUTELY NO WARRANTY.
See the "LICENSE" file distributed with this software for details.

OpenFAST-v3.1.0
Compile Info:

Compiler: Intel(R) Fortran Compiler 1900
Architecture: 64 bit
Precision: single
OpenMP: No
Date: Mar 08 2022
Time: 10:53:02
Execution Info:
Date: 05/17/2022
Time: 17:06:08+0530

OpenFAST input file heading:
FAST Certification Test #22: NREL 5.0 MW Baseline Wind Turbine with ITI Barge Configuration,
for use in offshore analysis
Running ElastoDyn.
Nodal outputs section of ElastoDyn input file not found or improperly formatted.
Running InflowWind.
Reading a 31x31 grid (145 m wide, 17.5 m to 162.5 m above ground) with a characteristic wind
speed of 12 m/s. This full-field file was generated by TurbSim (v1.06.00, 21-Sep-2012) on
07-Jan-2014 at 12:50:45.
Processed 1442 time steps of 20-Hz full-field data (72.05 seconds).
Running HydroDyn.
Generating incident wave kinematics and current time history.
Reading in WAMIT output with root name ".../5MW_Baseline/HydroData/Barge".
Computing radiation impulse response functions and wave diffraction forces.
Using SS_Radiation Module, with 30 of 30 radiation states
MAP++ environment properties (set externally)...
Gravity constant          [m/s^2]  : 9.81
Sea density               [kg/m^3] : 1025.00
Water depth               [m]      : 200.00
Vessel reference position [m]      : 0.00 , 0.00 , 0.00
FAST_InitializeAll:SetVTKParameters:Cannot do surface visualization without using AeroDyn.
OpenFAST encountered an error during module initialization.
Simulation error level: FATAL ERROR
Aborting OpenFAST.
PS C:\jb\r-test-061441958a2eef7f494d69ee097f8ec050d5a129\glue-codes\openfast\5MW_ITIBarge_DLL_WTurb_WavesIrr>

Dear @yuangao0916,
I'm not sure what would cause FAST.Farm to abort without an error.  Can you share your full set of input files so that I can see if I can reproduce the error?
Best regards,

Dear @jjonkman,
I am quite confused about this because it works ok with my non-parallel version (it just run the simulation to the end), but once I change to this _OMP.exe file, it abort like this..
The following is my .fstf input file:
FAST.Farm v1.00.* INPUT FILE
Sample FAST.Farm input file
--- SIMULATION CONTROL ---
True              Echo               Echo input data to .ech? (flag)
FATAL              AbortLevel         Error level when simulation should abort (string) {"WARNING", "SEVERE", "FATAL"}
2800.0              TMax               Total run time (s) [>=0.0]
False              UseSC              Use a super controller? (flag)
2                  Mod_AmbWind        Ambient wind model (-) (switch) {1: high-fidelity precursor in VTK format, 2: one InflowWind module, 3: multiple instances of InflowWind module}
--- SUPER CONTROLLER --- [used only for UseSC=True]
"SC_DLL.dll"       SC_FileName        Name/location of the dynamic library {.dll [Windows] or .so [Linux]} containing the Super Controller algorithms (quoated string)
--- AMBIENT WIND: PRECURSOR IN VTK FORMAT --- [used only for Mod_AmbWind=1]
3.0                DT_Low-VTK         Time step for low -resolution wind data input files  ; will be used as the global FAST.Farm time step (s) [>0.0]
0.1                DT_High-VTK        Time step for high-resolution wind data input files   (s) [>0.0]
"unused"           WindFilePath       Path name to VTK wind data files from precursor (string)
False              ChkWndFiles        Check all the ambient wind files for data consistency? (flag)
--- AMBIENT WIND: INFLOWWIND MODULE --- [used only for Mod_AmbWind=2 or 3]
3.0                DT_Low             Time step for low -resolution wind data interpolation; will be used as the global FAST.Farm time step (s) [>0.0]
0.1                DT_High            Time step for high-resolution wind data interpolation (s) [>0.0]
313                NX_Low             Number  of low -resolution spatial nodes in X direction for wind data interpolation (-) [>=2]
101                NY_Low             Number  of low -resolution spatial nodes in Y direction for wind data interpolation (-) [>=2]
35                 NZ_Low             Number  of low -resolution spatial nodes in Z direction for wind data interpolation (-) [>=2]
-183.07            X0_Low             Origin  of low -resolution spatial nodes in X direction for wind data interpolation (m)
-500.0             Y0_Low             Origin  of low -resolution spatial nodes in Y direction for wind data interpolation (m)
-15.0              Z0_Low             Origin  of low -resolution spatial nodes in Z direction for wind data interpolation (m) [5]
10.17              dX_Low             Spacing of low -resolution spatial nodes in X direction for wind data interpolation (m) [>0.0]
10.0               dY_Low             Spacing of low -resolution spatial nodes in Y direction for wind data interpolation (m) [>0.0]
10.0               dZ_Low             Spacing of low -resolution spatial nodes in Z direction for wind data interpolation (m) [>0.0]
18                 NX_High            Number  of high-resolution spatial nodes in X direction for wind data interpolation (-) [>=2]
17                 NY_High            Number  of high-resolution spatial nodes in Y direction for wind data interpolation (-) [>=2]
17                 NZ_High            Number  of high-resolution spatial nodes in Z direction for wind data interpolation (-) [>=2]
"InflowWind.dat"   InflowFile         Name of file containing InflowWind module input parameters (quoted string)
--- WIND TURBINES ---
3                  NumTurbines        Number of wind turbines (-) [>=1]                          [last 6 columns below used only for Mod_AmbWind=2 or 3]
WT_X    WT_Y   WT_Z   WT_FASTInFile     X0_High  Y0_High  Z0_High  dX_High  dY_High  dZ_High
(m)     (m)    (m)    (string)          (m)      (m)      (m)      (m)      (m)      (m)
5.0     0.0    0.0    "FFTest_WT1.fst"   -77.7    -80.0   5.0      40.17    40.0     30.0
1013.0  0.0    0.0    "FFTest_WT2.fst"   932.37   -180.0   5.0      40.17    40.0     30.0
2021.0  0.0    0.0    "FFTest_WT3.fst"  1942.44   -280.0   5.0      40.17    40.0     30.0
--- WAKE DYNAMICS ---
5.0                dr                 Radial increment of radial finite-difference grid (m) [>0.0]
40                 NumRadii           Number of radii in the radial finite-difference grid (-) [>=2]
136                NumPlanes          Number of wake planes (-) [>=2]
DEFAULT            f_c                Cutoff (corner) frequency of the low-pass time-filter for the wake advection, deflection, and meandering model (Hz) [>0.0] or DEFAULT [DEFAULT=0.0007]
DEFAULT            C_HWkDfl_O         Calibrated parameter in the correction for wake deflection defining the horizontal offset at the rotor                                               (m    ) or DEFAULT [DEFAULT= 0.0  ]
DEFAULT            C_HWkDfl_OY        Calibrated parameter in the correction for wake deflection defining the horizontal offset at the rotor scaled with                         yaw error (m/deg) or DEFAULT [DEFAULT= 0.3  ]
DEFAULT            C_HWkDfl_x         Calibrated parameter in the correction for wake deflection defining the horizontal offset              scaled with downstream distance               (-    ) or DEFAULT [DEFAULT= 0.0  ]
DEFAULT            C_HWkDfl_xY        Calibrated parameter in the correction for wake deflection defining the horizontal offset              scaled with downstream distance and yaw error (1/deg) or DEFAULT [DEFAULT=-0.004]
DEFAULT            C_NearWake         Calibrated parameter for the near-wake correction (-) [>1.0 and <2.5] or DEFAULT [DEFAULT=1.8]
DEFAULT            k_vAmb             Calibrated parameter for the influence of ambient turbulence in the eddy viscosity (-) [>=0.0] or DEFAULT [DEFAULT=0.05 ]
DEFAULT            k_vShr             Calibrated parameter for the influence of the shear layer    in the eddy viscosity (-) [>=0.0] or DEFAULT [DEFAULT=0.016]
DEFAULT            C_vAmb_DMin        Calibrated parameter in the eddy viscosity filter function for ambient turbulence defining the transitional diameter fraction between the minimum and exponential regions (-) [>=0.0          ] or DEFAULT [DEFAULT= 0.0 ]
DEFAULT            C_vAmb_DMax        Calibrated parameter in the eddy viscosity filter function for ambient turbulence defining the transitional diameter fraction between the exponential and maximum regions (-) [> C_vAmb_DMin  ] or DEFAULT [DEFAULT= 1.0 ]
DEFAULT            C_vAmb_FMin        Calibrated parameter in the eddy viscosity filter function for ambient turbulence defining the value in the minimum region                                                (-) [>=0.0 and <=1.0] or DEFAULT [DEFAULT= 1.0 ]
DEFAULT            C_vAmb_Exp         Calibrated parameter in the eddy viscosity filter function for ambient turbulence defining the exponent in the exponential region                                         (-) [> 0.0          ] or DEFAULT [DEFAULT= 0.01]
DEFAULT            C_vShr_DMin        Calibrated parameter in the eddy viscosity filter function for the shear layer    defining the transitional diameter fraction between the minimum and exponential regions (-) [>=0.0          ] or DEFAULT [DEFAULT= 3.0 ]
DEFAULT            C_vShr_DMax        Calibrated parameter in the eddy viscosity filter function for the shear layer    defining the transitional diameter fraction between the exponential and maximum regions (-) [> C_vShr_DMin  ] or DEFAULT [DEFAULT=25.0 ]
DEFAULT            C_vShr_FMin        Calibrated parameter in the eddy viscosity filter function for the shear layer    defining the value in the minimum region                                                (-) [>=0.0 and <=1.0] or DEFAULT [DEFAULT= 0.2 ]
DEFAULT            C_vShr_Exp         Calibrated parameter in the eddy viscosity filter function for the shear layer    defining the exponent in the exponential region                                         (-) [> 0.0          ] or DEFAULT [DEFAULT= 0.1 ]
DEFAULT            Mod_WakeDiam       Wake diameter calculation model (-) (switch) {1: rotor diameter, 2: velocity based, 3: mass-flux based, 4: momentum-flux based} or DEFAULT [DEFAULT=1]
DEFAULT            C_WakeDiam         Calibrated parameter for wake diameter calculation (-) [>0.0 and <0.99] or DEFAULT [DEFAULT=0.95] [unused for Mod_WakeDiam=1]
DEFAULT            Mod_Meander        Spatial filter model for wake meandering (-) (switch) {1: uniform, 2: truncated jinc, 3: windowed jinc} or DEFAULT [DEFAULT=3]
DEFAULT            C_Meander          Calibrated parameter for wake meandering (-) [>=1.0] or DEFAULT [DEFAULT=1.9]
--- VISUALIZATION ---
False              WrDisWind          Write low- and high-resolution disturbed wind data to .Low.Dis.t.vtk etc.? (flag)
1                  NOutDisWindXY      Number of XY planes for output of disturbed wind data across the low-resolution domain to .Low.DisXY<n_out>.t.vtk (-) [0 to 9]
90.0               OutDisWindZ        Z coordinates of XY planes for output of disturbed wind data across the low-resolution domain (m) [1 to NOutDisWindXY] [unused for NOutDisWindXY=0]
0                  NOutDisWindYZ      Number of YZ planes for output of disturbed wind data across the low-resolution domain to /Low.DisYZ<n_out>.t.vtk (-) [0 to 9]
748.0, 1252.0, 1378.0, 1504.0, 1630.0, 1756.0, 1882.0, 2008.0   OutDisWindX        X coordinates of YZ planes for output of disturbed wind data across the low-resolution domain (m) [1 to NOutDisWindYZ] [unused for NOutDisWindYZ=0]
0                  NOutDisWindXZ      Number of XZ planes for output of disturbed wind data across the low-resolution domain to /Low.DisXZ<n_out>.t.vtk (-) [0 to 9]
0.0                OutDisWindY        Y coordinates of XZ planes for output of disturbed wind data across the low-resolution domain (m) [1 to NOutDisWindXZ] [unused for NOutDisWindXZ=0]
3.0                WrDisDT            Time step for disturbed wind visualization output (s) [>0.0] or DEFAULT [DEFAULT=DT_Low or DT_Low-VTK] [unused for WrDisWind=False and NOutDisWindXY=NOutDisWindYZ=NOutDisWindXZ=0]
--- OUTPUT ---
True               SumPrint           Print summary data to .sum? (flag)
99999.9            ChkptTime          Amount of time between creating checkpoint files for potential restart (s) [>0.0]
0.0              TStart             Time to begin tabular output (s) [>=0.0]
1                  OutFileFmt         Format for tabular (time-marching) output file (switch) {1: text file [.out], 2: binary file [.outb], 3: both}
True               TabDelim           Use tab delimiters in text tabular output file? (flag) {uses spaces if False}
"ES10.3E2"         OutFmt             Format used for text tabular output, excluding the time channel.  Resulting field should be 10 characters. (quoted string)
20                 NOutRadii          Number of radial nodes         for wake output for an individual rotor (-) [0 to 20]
0, 1, 2, 3, 4, 5, 7, 9, 11, 13, 15, 16, 17, 18, 19, 21, 24, 28, 33, 39  OutRadii           List of radial nodes         for wake output for an individual rotor (-) [1 to NOutRadii] [unused for NOutRadii=0]
7                  NOutDist           Number of downstream distances for wake output for an individual rotor (-) [0 to 9 ]
252.0, 378.0, 504.0, 630.0, 756.0, 882.0, 1008.0          OutDist            List of downstream distances for wake output for an individual rotor (m) [1 to NOutDist ] [unused for NOutDist =0]
1                  NWindVel           Number of points for wind output (-) [0 to 9]
1000.0             WindVelX           List of coordinates in the X direction for wind output (m) [1 to NWindVel] [unused for NWindVel=0]
0.0                WindVelY           List of coordinates in the Y direction for wind output (m) [1 to NWindVel] [unused for NWindVel=0]
90.0               WindVelZ           List of coordinates in the Z direction for wind output (m) [1 to NWindVel] [unused for NWindVel=0]
OutList            The next line(s) contains a list of output parameters.  See OutListParameters.xlsx for a listing of available output channels (quoted string)
"RtAxsXT1     , RtAxsYT1     , RtAxsZT1"
"RtPosXT1     , RtPosYT1     , RtPosZT1"
"YawErrT1"
"TIAmbT1"
"CtT1N01      , CtT1N02      , CtT1N03      , CtT1N04      , CtT1N05      , CtT1N06      , CtT1N07      , CtT1N08      , CtT1N09      , CtT1N10      , CtT1N11      , CtT1N12      , CtT1N13      , CtT1N14      , CtT1N15      , CtT1N16      , CtT1N17      , CtT1N18      , CtT1N19      , CtT1N20"
"WkAxsXT1D1   , WkAxsXT1D2   , WkAxsXT1D3   , WkAxsXT1D4   , WkAxsXT1D5   , WkAxsXT1D6   , WkAxsXT1D7"
"WkAxsYT1D1   , WkAxsYT1D2   , WkAxsYT1D3   , WkAxsYT1D4   , WkAxsYT1D5   , WkAxsYT1D6   , WkAxsYT1D7"
"WkAxsZT1D1   , WkAxsZT1D2   , WkAxsZT1D3   , WkAxsZT1D4   , WkAxsZT1D5   , WkAxsZT1D6   , WkAxsZT1D7"
"WkPosXT1D1   , WkPosXT1D2   , WkPosXT1D3   , WkPosXT1D4   , WkPosXT1D5   , WkPosXT1D6   , WkPosXT1D7"
"WkPosYT1D1   , WkPosYT1D2   , WkPosYT1D3   , WkPosYT1D4   , WkPosYT1D5   , WkPosYT1D6   , WkPosYT1D7"
"WkPosZT1D1   , WkPosZT1D2   , WkPosZT1D3   , WkPosZT1D4   , WkPosZT1D5   , WkPosZT1D6   , WkPosZT1D7"
"WkDfVxT1N01D1, WkDfVxT1N02D1, WkDfVxT1N03D1, WkDfVxT1N04D1, WkDfVxT1N05D1, WkDfVxT1N06D1, WkDfVxT1N07D1, WkDfVxT1N08D1, WkDfVxT1N09D1, WkDfVxT1N10D1, WkDfVxT1N11D1, WkDfVxT1N12D1, WkDfVxT1N13D1, WkDfVxT1N14D1, WkDfVxT1N15D1, WkDfVxT1N16D1, WkDfVxT1N17D1, WkDfVxT1N18D1, WkDfVxT1N19D1, WkDfVxT1N20D1"
"WkDfVxT1N01D2, WkDfVxT1N02D2, WkDfVxT1N03D2, WkDfVxT1N04D2, WkDfVxT1N05D2, WkDfVxT1N06D2, WkDfVxT1N07D2, WkDfVxT1N08D2, WkDfVxT1N09D2, WkDfVxT1N10D2, WkDfVxT1N11D2, WkDfVxT1N12D2, WkDfVxT1N13D2, WkDfVxT1N14D2, WkDfVxT1N15D2, WkDfVxT1N16D2, WkDfVxT1N17D2, WkDfVxT1N18D2, WkDfVxT1N19D2, WkDfVxT1N20D2"
"WkDfVxT1N01D3, WkDfVxT1N02D3, WkDfVxT1N03D3, WkDfVxT1N04D3, WkDfVxT1N05D3, WkDfVxT1N06D3, WkDfVxT1N07D3, WkDfVxT1N08D3, WkDfVxT1N09D3, WkDfVxT1N10D3, WkDfVxT1N11D3, WkDfVxT1N12D3, WkDfVxT1N13D3, WkDfVxT1N14D3, WkDfVxT1N15D3, WkDfVxT1N16D3, WkDfVxT1N17D3, WkDfVxT1N18D3, WkDfVxT1N19D3, WkDfVxT1N20D3"
"WkDfVxT1N01D4, WkDfVxT1N02D4, WkDfVxT1N03D4, WkDfVxT1N04D4, WkDfVxT1N05D4, WkDfVxT1N06D4, WkDfVxT1N07D4, WkDfVxT1N08D4, WkDfVxT1N09D4, WkDfVxT1N10D4, WkDfVxT1N11D4, WkDfVxT1N12D4, WkDfVxT1N13D4, WkDfVxT1N14D4, WkDfVxT1N15D4, WkDfVxT1N16D4, WkDfVxT1N17D4, WkDfVxT1N18D4, WkDfVxT1N19D4, WkDfVxT1N20D4"
"WkDfVxT1N01D5, WkDfVxT1N02D5, WkDfVxT1N03D5, WkDfVxT1N04D5, WkDfVxT1N05D5, WkDfVxT1N06D5, WkDfVxT1N07D5, WkDfVxT1N08D5, WkDfVxT1N09D5, WkDfVxT1N10D5, WkDfVxT1N11D5, WkDfVxT1N12D5, WkDfVxT1N13D5, WkDfVxT1N14D5, WkDfVxT1N15D5, WkDfVxT1N16D5, WkDfVxT1N17D5, WkDfVxT1N18D5, WkDfVxT1N19D5, WkDfVxT1N20D5"
"WkDfVxT1N01D6, WkDfVxT1N02D6, WkDfVxT1N03D6, WkDfVxT1N04D6, WkDfVxT1N05D6, WkDfVxT1N06D6, WkDfVxT1N07D6, WkDfVxT1N08D6, WkDfVxT1N09D6, WkDfVxT1N10D6, WkDfVxT1N11D6, WkDfVxT1N12D6, WkDfVxT1N13D6, WkDfVxT1N14D6, WkDfVxT1N15D6, WkDfVxT1N16D6, WkDfVxT1N17D6, WkDfVxT1N18D6, WkDfVxT1N19D6, WkDfVxT1N20D6"
"WkDfVxT1N01D7, WkDfVxT1N02D7, WkDfVxT1N03D7, WkDfVxT1N04D7, WkDfVxT1N05D7, WkDfVxT1N06D7, WkDfVxT1N07D7, WkDfVxT1N08D7, WkDfVxT1N09D7, WkDfVxT1N10D7, WkDfVxT1N11D7, WkDfVxT1N12D7, WkDfVxT1N13D7, WkDfVxT1N14D7, WkDfVxT1N15D7, WkDfVxT1N16D7, WkDfVxT1N17D7, WkDfVxT1N18D7, WkDfVxT1N19D7, WkDfVxT1N20D7"
"WkDfVrT1N01D1, WkDfVrT1N02D1, WkDfVrT1N03D1, WkDfVrT1N04D1, WkDfVrT1N05D1, WkDfVrT1N06D1, WkDfVrT1N07D1, WkDfVrT1N08D1, WkDfVrT1N09D1, WkDfVrT1N10D1, WkDfVrT1N11D1, WkDfVrT1N12D1, WkDfVrT1N13D1, WkDfVrT1N14D1, WkDfVrT1N15D1, WkDfVrT1N16D1, WkDfVrT1N17D1, WkDfVrT1N18D1, WkDfVrT1N19D1, WkDfVrT1N20D1"
"WkDfVrT1N01D2, WkDfVrT1N02D2, WkDfVrT1N03D2, WkDfVrT1N04D2, WkDfVrT1N05D2, WkDfVrT1N06D2, WkDfVrT1N07D2, WkDfVrT1N08D2, WkDfVrT1N09D2, WkDfVrT1N10D2, WkDfVrT1N11D2, WkDfVrT1N12D2, WkDfVrT1N13D2, WkDfVrT1N14D2, WkDfVrT1N15D2, WkDfVrT1N16D2, WkDfVrT1N17D2, WkDfVrT1N18D2, WkDfVrT1N19D2, WkDfVrT1N20D2"
"WkDfVrT1N01D3, WkDfVrT1N02D3, WkDfVrT1N03D3, WkDfVrT1N04D3, WkDfVrT1N05D3, WkDfVrT1N06D3, WkDfVrT1N07D3, WkDfVrT1N08D3, WkDfVrT1N09D3, WkDfVrT1N10D3, WkDfVrT1N11D3, WkDfVrT1N12D3, WkDfVrT1N13D3, WkDfVrT1N14D3, WkDfVrT1N15D3, WkDfVrT1N16D3, WkDfVrT1N17D3, WkDfVrT1N18D3, WkDfVrT1N19D3, WkDfVrT1N20D3"
"WkDfVrT1N01D4, WkDfVrT1N02D4, WkDfVrT1N03D4, WkDfVrT1N04D4, WkDfVrT1N05D4, WkDfVrT1N06D4, WkDfVrT1N07D4, WkDfVrT1N08D4, WkDfVrT1N09D4, WkDfVrT1N10D4, WkDfVrT1N11D4, WkDfVrT1N12D4, WkDfVrT1N13D4, WkDfVrT1N14D4, WkDfVrT1N15D4, WkDfVrT1N16D4, WkDfVrT1N17D4, WkDfVrT1N18D4, WkDfVrT1N19D4, WkDfVrT1N20D4"
"WkDfVrT1N01D5, WkDfVrT1N02D5, WkDfVrT1N03D5, WkDfVrT1N04D5, WkDfVrT1N05D5, WkDfVrT1N06D5, WkDfVrT1N07D5, WkDfVrT1N08D5, WkDfVrT1N09D5, WkDfVrT1N10D5, WkDfVrT1N11D5, WkDfVrT1N12D5, WkDfVrT1N13D5, WkDfVrT1N14D5, WkDfVrT1N15D5, WkDfVrT1N16D5, WkDfVrT1N17D5, WkDfVrT1N18D5, WkDfVrT1N19D5, WkDfVrT1N20D5"
"WkDfVrT1N01D6, WkDfVrT1N02D6, WkDfVrT1N03D6, WkDfVrT1N04D6, WkDfVrT1N05D6, WkDfVrT1N06D6, WkDfVrT1N07D6, WkDfVrT1N08D6, WkDfVrT1N09D6, WkDfVrT1N10D6, WkDfVrT1N11D6, WkDfVrT1N12D6, WkDfVrT1N13D6, WkDfVrT1N14D6, WkDfVrT1N15D6, WkDfVrT1N16D6, WkDfVrT1N17D6, WkDfVrT1N18D6, WkDfVrT1N19D6, WkDfVrT1N20D6"
"WkDfVrT1N01D7, WkDfVrT1N02D7, WkDfVrT1N03D7, WkDfVrT1N04D7, WkDfVrT1N05D7, WkDfVrT1N06D7, WkDfVrT1N07D7, WkDfVrT1N08D7, WkDfVrT1N09D7, WkDfVrT1N10D7, WkDfVrT1N11D7, WkDfVrT1N12D7, WkDfVrT1N13D7, WkDfVrT1N14D7, WkDfVrT1N15D7, WkDfVrT1N16D7, WkDfVrT1N17D7, WkDfVrT1N18D7, WkDfVrT1N19D7, WkDfVrT1N20D7"
END of input file (the word "END" must appear in the first 3 columns of this last OutList line)

@jjonkman  and @yuangao0916
this may be a bug with opening files for writing.  When run in parrallel, I have occasionally seen issues with a unit number for file writing getting issued by GetNewUnit, and another process getting issued the same unit number before either actually opens the file.  I think this occasionally leads to strange crashes from the conflicting unit numbers.  This should be caught internally and the program should gracefully end, but given the state of error handling in some of the modules (HD, AWAE for example) I shouldn't be surprised it isn't.  If this is the cause, we need a long term solution for it.
Andy

Dear @andrew-platt
Thanks for the information.
I think this might be the cause, but I haven't gotten it successfully run in the parallel case even once. - I used the same input files and controllers which was ok for the non-parallel cases.
For now, I will focus on the non-parallel once then.
Thank you again.
Yours sincerely,
Yuan

Thanks, @andrew-platt, for the suggestion.
@yuangao0916 -- Can you confirm that you are running the precompiled Windows binary version of FAST.Farm provided by NREL (FAST.Farm_x64_OMP.exe, available from here: https://github.com/OpenFAST/openfast/releases) and that you have installed the Intel Fortran redistributable package and running from the Intel command prompt that loads the Intel libraries?
Best regards,

Dear @jjonkman ,
Yes, that is what I did.
Yours sincerely,
Yuan


Numerical correctness issue

Hi,
I'm trying to convert a pre-trained model (TensorFlow) created by David Sandberg as part of the FaceNet (https://github.com/davidsandberg/facenet) project but I'm getting some anomalies. The project does not output classifications BUT it returns the embeddings for a particular image. I'm able to convert the model to CoreML but when I run the 'ssd_example.ipynb' playbook (obviously modified to compare the 128 measurements, instead of the box_encodings and scores) I get different values.

Can someone please tell me if I'm doing something wrong??
Thx

The CoreML output and TF output will never match exactly. Reasons for that:

the default execution path for CoreML (GPU) uses lower precision (float 16)
even when the forceCPU flag is used to use the float 32 bit path, there might be differences because of different optimized algorithms used to evaluate convolutions

Yes it looks correct and you should be able to use it in your iOS app.
Although it wouldn’t hurt to first try it in python with the actual data that you expect in your app. For example if you are doing detection you can plot the bounding boxes and check whether they match reasonably with the ones you get with TF.
How much accuracy you really need depends on your application. For instance, in classification you just want the top few classes to match.
You can always use the forceCPU flag to get better accuracy.

Thank you @aseemw, you're a star! I'll go ahead and close the issue.

@jacogreyling Tried for a while to convert to CoreML and gave up; trying it again. I am doing this:
tfcoreml.convert(tf_model_path = '20180402-114759.pb',
mlmodel_path = 'Test.mlmodel',
output_feature_names = ['softmax:0'],
input_name_shape_dict = {'input:0' : [1, 160, 160, 3]})
And this is what I get:

Please provide the shape for the input phase_train:0 through the argument 'input_name_shape_dict'

Could you please provide any insight on what's wrong? What's the name/shape of the input? What about the name/shape of the embedding?What do you mean by

obviously modified to compare the 128 measurements, instead of the box_encodings and scores

Any help would be very appreciated!

@jacogreyling ^ Any help would be very appreciated!


cache:clear doesn't remove oxCache (EE Edition)

There must be a possibility to remove oxCache with cache:clear command. This must be patched in both 1.1 and 1.2 releases. Also we may need a flag --files-only to support clearing files only because some setups may rely on that.

This is already solved within https://github.com/EllisV/oxid-console/commit/c3a0e3ab87f2e670627de2580bd41f8e56e0c862
It's released within v1.1.7 and v1.2.3


Unexpected handling of errors with expose=true

I recently came across a situation where I wanted to throw an error from within a koa middleware and have it both exposed to the client and conditionally logged to the console. My method for handling this was:

Add a middleware high up the stack for catching errors and conditionally passing them to app.emit('error', ...):app.use(function *error(next){
  try {
    yield next;
    if (404 == this.response.status && !this.response.body) this.throw(404);
  } catch (err) {
    this.status = err.status || 500;

    // application
    (err.log !== false) && app.emit('error', err, this);

    // accepted types
    switch (this.accepts('text', 'json')) {
      case 'text':
        this.type = 'text/plain';
        if (env === 'development') this.body = err.message
        else if (err.expose_to_client) this.body = err.message
        else throw err;
        break;

      case 'json':
        this.type = 'application/json';
        if (env === 'development') this.body = { error: err.message }
        else if (err.expose_to_client) this.body = { error: err.message }
        else this.body = { error: http.STATUS_CODES[this.status] }
        break;
    }
  }
});

Create an Error object and give it err.expose = true and err.log = true (or err.log = false in the instance where the error should not be logged) from within another middleware and throw it

This led me to discover that if an error err is marked with err.expose = true, Koa's default app.on('error', ...) handler will ignore it, as per this line: https://github.com/koajs/koa/blob/master/lib/application.js#L173
Does it really make sense for the default error handler to not log errors that are exposed to the client?

I think it's reasonable for a default, doesn't really matter I suppose. It's definitely ideal to use something custom or like koajs/logger for "real" logging

True, and in fact I am using koajs/logger in this instance, but that's just for logging the request/response. I am using app.emit('error', ...) for logging the error though (which I thought was the standard technique for handling errors?).

Ah sorry you're right, I forgot we re-throw there. I guess the difference is that the exposed ones are supposed to represent user errors, so they should be displayed somewhere in UI or in the response

Yeah, no problem, I just wanted to bring it up here since it took me off guard. Definitely not something that needs to be changed within the code, since as you said, it's reasonable for a default. We should, however, document the currently-undocumented err.expose (and err.silent) functionality somewhere in the docs.
The fix I've landed with here is to override the default error handler via:
app.on('error', log);

Such that any error which passes through app.emit will always land in the log.

@cmbankester we would love a doc PR!


Speedup tests by using pytest-xdist

Looks like this adds a fair amount of complexity, but doesn't necessarily speed things up much :(


add support for hashing records by a specified key column

being able to hash items pulled from postgres by some specified key column integrates well with the fetch_one config option, allowing applications to later update a specific item in a collection by that key rather than providing an index into an array

Hey @treysidechain thanks for your contribution.
@orishavit will review.

While this was never merged, I believe https://github.com/permitio/opal-fetcher-postgres/pull/16 implements this behaviour - if you're reading this the functionality is already available by now :)

As per @philipclaesson 's comment - this was closed by #16
Still appreciate your contribution here @treysidechain  - message us with shipping details - if you'd like a swag package :)


Connection Error

Reported by Craige1Emmott, May 16, 2013
JMM Server can sometimes spam out error messages relating to a null object reference with the connection.
log attached.
Error example
Error|AniDBHelper.Login => AniDBCommand_Login.Process => AniDBUDPCommand.ProcessCommand System.ArgumentNullException: Value cannot be null.
Parameter name: remoteEP
   at System.Net.Sockets.Socket.SendTo(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, EndPoint remoteEP)
   at System.Net.Sockets.Socket.SendTo(Byte[] buffer, EndPoint remoteEP)
   at AniDBAPI.Commands.AniDBUDPCommand.ProcessCommand(Socket& soUDP, IPEndPoint& remoteIpEndPoint, String sessionID, Encoding enc) in C:\Projects\SVN\JMM\trunk\JMMServer\JMMServer\AniDB_API\Commands\AniDBUDPCommand.cs:line 105

@craige1 do you still encounter this error? I'm unable to reproduce.

Look thru logs of almost 1 year now and not null exception with similar error.
Mayby something related with OS


⚠ Fortnite has degraded performance

In a87038d, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1507 ms

Resolved: Fortnite performance has improved in e387912.


cannot encode a dotted pair

Surprisingly JZON fails to encode a dotted pair, as it assumes it will be able to call length on the cdr
(jzon:stringify '(1 . 2))

as a side note, this issue (together with this one) was uncovered while testing cl-transit, which uses jzon for the JSON part.

Hi - Yes, jzon used to be clever about things like dotted pairs but it was scaled back. Instead it only encodes proper lists.
But I am a fan of "it just works". What do you believe a dotted pair should stringify to?

IMO a dotted pair ought to  be encoded as a list with 2 elements in it.

Alright. I appreciate it. I'll look through my notes later to see what past me had to say about this and get back to you.
I don't see the harm now that we don't do fancy alist/plist heuristic detection.
Thanks. And thanks again for the float report - I can't believe I forgot to test the trivial case on that one. Embarrassing.


Modify: DOSBoxStaging.DOSBoxStaging

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Links\dosbox.exe returned exit code: -1073741515

(Automated response - build 877.)

Not sure about the exit code number, may be a missing vc runtime or something similar. Or just a vm-related thing that can be waived.

https://github.com/microsoft/winget-pkgs/issues/107639


file-transfers: add (admin) HTTP endpoints for reading configs

Issue: https://github.com/moov-io/paygate/issues/147

Codecov Report

Merging #148 into master will decrease coverage by 3.91%.
The diff coverage is 57.56%.

@@            Coverage Diff             @@
##           master     #148      +/-   ##
==========================================
- Coverage   56.48%   52.56%   -3.92%
==========================================
  Files          26       27       +1
  Lines        3541     3641     +100
==========================================
- Hits         2000     1914      -86
- Misses       1145     1335     +190
+ Partials      396      392       -4

Impacted Files
Coverage Δ

main.go
0% <0%> (ø)
:arrow_up:

file_transfer_async.go
44.15% <100%> (-4.24%)
:arrow_down:

file_transfer_configs.go
55.67% <55.67%> (ø)

accounts.go
9.72% <0%> (-70.84%)
:arrow_down:

internal/database/mysql.go
31.16% <0%> (-44.16%)
:arrow_down:

ofac.go
38.13% <0%> (-35.6%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4f5b0c2...2c31204. Read the comment docs.


Redesign File Input

Instead of a single file input with "advanced options", use Parallel Boxes, each of which takes a file and exposes its own options.

Resolved by d34663fc4f99d700fa9799acc959386e6490da76


Update copyright

@samnela I think this build will be fix after #40 gets resolved.

Thank you @ramsey  and @AkshatSrivastava2