text:
When I run “sc = Synth(data,……n_optim=100)”, I get the error "ValueError: 'x0' must only have one dimension."

run code below , get the error "ValueError: 'x0' must only have one dimension."
# Fit synthetic control
sc = Synth(data, "gdp", "country", "year", 1990, "West Germany", n_optim=100)

maybe optimize.py should delete "size=1"？
else:
    #Dirichlet distribution returns a valid pmf over n_covariates states
    v_0 = self.original_data.rng.dirichlet(np.ones(data.n_covariates), size=1)
    if pen == "auto":
        #if pen =="auto", we have an additional parameter to optimize over, so we append it
        v_0 = np.append(v_0, self.original_data.rng.lognormal(1.5, 1, size=1)) #Still experimenting with what distribution is appropriate

I successfully ran it after removing the “size = 1” parameter


text:
Finish the plot functions in visualizer.py and test_visualizer

Finish the plot functions in visualizer.py (4 in total) and test_visualizer. Modify the exponential function in preproc.py

Good!

source: gharchive/pull-request

authors: FrankLeeX Oscarlight

license: mit

license_type: permissive

license_source: bigquery


text:
Check system architecture to avoid failure on ARM64

Describe the bug
Per issue #310 , Ostorlab runtime do not check system architecture and causes failures on ARM64.
Pending adding support to AM64, we must check for the host system architecture.
To Reproduce
Check #310.
Expected behavior
Raise an error and ask to run on a compatibility runtime for x64.
Desktop (please complete the following information):
ARM64 Mac M1.

PR merged. The failing tests were due to permissions issues.
Since the SSH was no longer needed, I had added a new PR #318 to remove it.
Kudos @jamu85 for the quick fix and thanks for your contribution!

source: gharchive/issue

repo: Ostorlab/ostorlab

license_source: github-api


text:
Ansible 2

Выполнено ДЗ №8

[x] Основное ДЗ
[ ] Задание со *

В процессе сделано:

все пункты из основного ДЗ

PR checklist

[x] Выставил label с номером домашнего задания
[ ] Выставил label с темой домашнего задания

Добрый день.
Ошибки видел, но понять проблему не могу. Как понимаю, там конфликт файлов inventory. Или inventory.yml написан не коррестно.

Поменял ^_^
А есть какой-то фикс для inventory?

license: MIT


text:
Disable logging in xclim.ensembles module?

Generic Issue
When importing clisops.subset.core and xclim.ensembles the logging output in the xclim.ensembles is somehow always sent to the console, or worse, to the jupyter notebook output window.
@Zeitsperre has been digging into this (see https://github.com/roocs/clisops/pull/216) but I am wondering just how critical it is to have a logger at all?
Notes - this seems to be the only submodule where a logger is used and as far as I can tell and only keeps track of 1) whether matplotlib is installed or not (for ensemble reduction graphs) or 2) which simulation is being accessed in the loop for the ensemble creation.
Code of Conduct

[X] #1040

Ok to scrap logging.

I'm OK as well for commenting the existing calls out, but this would be a good opportunity to drop-in loguru in its stead.

Ok to scrap clisops.

authors: Zeitsperre aulemahal huard tlogan2000

repo: Ouranosinc/xclim


text:
Complex Lazypipe channel with several sources and outputs?

Trying this again, the original issue was closed abruptly.
The assumption that my question is a "Gulp" issue is wrong @OverZealous , in fact, I posted code that clearly uses lazypipe.
I can merge streams using either the merge or event-stream libraries, thats not the issue. At the moment I am using a simple function as a re-usable unit for the several Gulp tasks. This has been in use for several months. I thought it would be nice to use Lazypipe which was developed to be used as reusable units/ channels.
My question is; How can I create a reusable lazypipe channel for a complex task that I would like to use in several projects.
I am trying to:
1. Concat and compress a set of CSS files
2. Inject both the compressed and non-compressed files in a HTML template
3. Make this a usable lazypipe channel for re-use over a set of projects
I have this so far
return lazypipe()
    .pipe(gulp.dest, output.non_compressed_path)
    .pipe(plugins.concat, optionsObj.filename)
    .pipe(plugins.csso, true)
    .pipe(gulp.dest, output.compressed_path)

To Inject the above in HTML templates however, the lazypipe source would have to start with the HTML template, so piping the result of the above would not work as in:
  // This has to starte with "gulp.src(templateName)" then pipe to below
 .pipe(plugins.inject, gulp.src(cssFiles, {read: false}), {name: 'test'})````

Can someone point me in the right direction? Thanks

There is no "someone", there is only me.  This is my project, I'm the sole maintainer.  I don't know why you think this is a public forum for support.  Try StackOverflow if you want answers to this sort of question.
This is not a lazypipe issue, it's not an issue at all.

Jeez, I have already decided on using the async lib instead this morning. Thanks for nothing.

authors: OverZealous kokujin

repo: OverZealous/lazypipe


text:
Remove slow effect from meteor strike

Created by: MaxwellJung
Victims hit by meteor strike are slowed in ow2 but not in ow1

mentioned in merge request ow1_emulator_backup!430

moved from ow1_emulator_backup#544

mentioned in merge request ow1_emulator_backup!414


text:
WIP: create a routing path object that manages routes

configure router to use this object
allow the current route path to be accessed from core_world
follow new interface in proceed to
This is functionally compatible with route recalculation as well
resolves #175
Needs unit tests

This change also relies on some logic introduced in route recalculation, so i'm rebasing it to that branch.
As such, closes #168

Haven't had a change to pull it down and look yet, but how does this affect the creation of the page_graph.dot?

No impact.
The routes that you can insert must have been defined on the page that they're being inserted against. (using add_route)
At some point i also intend to add the ability to dynamically define a route that you're inserting, something like
@world.current_route.insert_page(SomePage, using_route: [[:visit, :arg1, :arg2], :param])

So, a route would still be declared via add_route... what's the insert_route actually doing then?

It sets the next page the router will navigate to in your flow

Okay, so it forces what the next page actually is, yes? Just making sure I'm getting this right.

Yes, great when you have pages that conditionally show up based on selections.

At some point we're going to get to the point where you feed oz a bunch of different data and tell it to get to each page at the end of a flow lol. Perhaps just have like 90 randomly teenaged datasets per execution and have it basically do an exploratory test 90 times

repo: OzFramework/oz


text:
Training for multiple classes

Thank you for your work! I tried using it for training for more classes ( 6 classes ) on Lyft Dataset.  I updated input/bdd_input.py file to suit the needs of Lyft dataset.  It also required changing hypes/kittiBox.json to reflect new image dimensions. (height: 1024, width: 1248)
While trying to train, I ran into a few weird issues.

The loss function suddenly explodes and the program crashes with  OverflowError: value too large to convert to int.

Here is the sample output from training (showing exploding loss):

`2020-06-30 03:21:22,589 root INFO Step 0/140000: loss = 39.73; lr = 1.00e-05; 0.104 sec (per Batch); 48.1 imgs/sec
2020-06-30 03:21:23,009 root INFO       (raw)  Acc.: 0.12, Conf: 31.51, Box: 2.22, Weight: 0.38, Delta: 2.61
2020-06-30 03:21:23,009 root INFO    (smooth)  Acc.: 0.12, Conf: 31.51, Box: 2.22, Weight: 0.38, Delta: 2.61
2020-06-30 03:21:23,915 root INFO Drawing encoded images (data utils)

2020-06-30 03:22:54,322 root INFO Step 200/140000: loss = 32.08; lr = 1.00e-05; 1.826 sec (per Batch); 2.7 imgs/sec
2020-06-30 03:22:54,481 root INFO       (raw)  Acc.: 0.76, Conf: 41.94, Box: 1.88, Weight: 0.38, Delta: 0.05
2020-06-30 03:22:54,481 root INFO    (smooth)  Acc.: 0.15, Conf: 32.03, Box: 2.20, Weight: 0.38, Delta: 2.48
2020-06-30 03:23:15,353 root INFO Drawing encoded images (data utils)

2020-06-30 03:24:26,125 root INFO Step 400/140000: loss = 772.73; lr = 1.00e-05; 1.268 sec (per Batch); 3.9 imgs/sec
2020-06-30 03:24:26,274 root INFO       (raw)  Acc.: 0.85, Conf: 28.31, Box: 1.34, Weight: 0.38, Delta: 1316.65
2020-06-30 03:24:26,275 root INFO    (smooth)  Acc.: 0.18, Conf: 31.85, Box: 2.16, Weight: 0.38, Delta: 68.19
2020-06-30 03:25:08,447 root INFO Drawing encoded images (data utils)

2020-06-30 03:25:59,540 root INFO Step 600/140000: loss = 399236.34; lr = 1.00e-05; 0.850 sec (per Batch); 5.9 imgs/sec
2020-06-30 03:25:59,712 root INFO       (raw)  Acc.: 0.85, Conf: 19.65, Box: 1.41, Weight: 0.38, Delta: 314026.66
2020-06-30 03:25:59,715 root INFO    (smooth)  Acc.: 0.22, Conf: 31.24, Box: 2.12, Weight: 0.38, Delta: 15766.12
2020-06-30 03:27:03,137 root INFO Drawing encoded images (data utils)

2020-06-30 03:27:32,453 root INFO Step 800/140000: loss = 19764840.00; lr = 1.00e-05; 0.419 sec (per Batch); 11.9 imgs/sec
2020-06-30 03:27:32,613 root INFO       (raw)  Acc.: 0.85, Conf: 23.55, Box: 1.84, Weight: 0.39, Delta: 21771650.00
2020-06-30 03:27:32,614 root INFO    (smooth)  Acc.: 0.25, Conf: 30.85, Box: 2.11, Weight: 0.38, Delta: 1103560.25

2020-06-30 03:28:57,191 root INFO Step 1000/140000: loss = 166476288.00; lr = 1.00e-05; 1.692 sec (per Batch); 3.0 imgs/sec
2020-06-30 03:28:57,340 root INFO       (raw)  Acc.: 0.85, Conf: 29.38, Box: 2.21, Weight: 0.39, Delta: 186277808.00
2020-06-30 03:28:57,341 root INFO    (smooth)  Acc.: 0.28, Conf: 30.78, Box: 2.11, Weight: 0.38, Delta: 10362273.00
2020-06-30 03:28:57,392 root INFO Drawing encoded images (data utils)`

The bounding boxes start looking like dots in images denoting something is definitely wrong.

At 1st iteration, predicted boxes look normal:
predicted_boxes

Ground_truth

At 3rd Iteration, predicted boxes start looking like dots.
predicted_boxes

Ground_truth

Have you by any chance encountered something similar while dealing with the training.
Any insights into this from your expertise would be very useful.

Maybe the issue is the format of your bounding boxes? I have not looked into the Lyft dataset, but sometimes the representation of the bounding boxes are different between different datasets. Make sure that the training data from Lyft corresponds to the Kitti format, and if not, you need to convert it to the right format (which is shown for BDD in bdd_input.py). In addition, you might need to change the eval to suit your needs (bdd_eval.py also contains a list CLASSES which contains the classes you want to evaluate).
Also, the projected ground truth boxes does not seem totally accurate, but I can not say for sure without looking at the training data. Can you verify that the ground truth boxes are projected the same way independent of this project?

It seems like the formatting for the bounding boxes is consistent with the bdd_dataset. To reduce the complexity and narrow done the source of error, I tried training KittiBox with a single class(car detector) and it works fine.
The output looks like

This makes me think, if the error is creeping not from data loading but somewhere else. Did you try training a multi-class detector using this branch? Do you think there might me some modifications needed to the file decoder/fastbox.py ? Any suggestions would be really appreciated.
I also verified the projection independent of the project and it looks okay.

repo: Ozzyz/KittiBox


text:
Latest version broke Symbol Browser

The latest version has completely broken the symbol browser in ST3 where the window is filled with everything
WITHOUT:

Installed:

As you can see with it being installed, it's completely filled the symbol browser with everything single variable or mention of a variable in the current file

Sorry for the issue and my late reply. I added too many things to the symbols list. I'll remove everything else in the symbols list except the mixin and function definition. Does that sound good? Or what other elements would you like to list in the symbols list?

Is it possible to a set a scope as well, as this is affecting non-scss files? Mixins and functions are a good idea though.

This was also reported on the Sublime Text forum:

https://forum.sublimetext.com/t/goto-symbol-not-working/33653 Goto Symbol not working?

The user had to revert Sublime Text to a clean install, and reintroduce his packages until find out this package was causing the problem.

Your preferences selector was the following:
<string>entity.name.tag, entity.other.attribute-name.id, entity.other.attribute-name.class, variable</string>

Any region matching that selector in any view would get added to the symbol list. Notably, each variable occurance (not definition!). By convention, definitions are scoped as entity.name.<something>, e.g. entity.name.function, and you should look into adding that to the symol list. You should also tie the selector to your syntax only by being more explicit, e.g. entity.name.function.sass or source.sass entity.name.

I am really sorry about the issue. I have removed my stupid preferences, therefore only mixin and function definitions can be listed in the symbols list.

Great thanks,

authors: FichteFoll P233 evandrocoan leereichardt


text:
登录一个账号后无法自动刷新

左下角始终是空白头像，没法再次登录另一个账号
Microsoft Edge版本 114.0.1823.58 (正式版本) (64 位)

使用相同版本测试，并未发现此问题。

貌似和其他去广告拓展冲突了，我把所有拓展全部关闭后正常了，然后又全部一个个打开之后还是正常，可能是偶发性的bug


text:
How to create groups via PermissionBackend?

Hey, after updating to the latest version I have some conflicts in my plugin.
The createGroup()-method seems to be gone and I can not find any replacement for it.
Can you tell me if it still posible to create groups (programmatically) or what to do otherwise?
Thanks for your great work!

Found it.
PermissionManager.getGroup("bla").save();
PermissionManager.getGroup("bla").remove();

Excellent!

repo: PEXPlugins/PermissionsEx


text:
Essentials nicknames not working

is there any way to integrate essentials nick command with chat manager,
people have claimed to have done it but i have no idea how so any info would be great.
thanks

Please post this ticket to ChatManager issue tracker.
https://github.com/PEXPlugins/ChatManager


text:
Add Potions Reference

Adds potions reference page for damage values, splash potions as damage value determines potion colour.
Update links to reference the reference page
Updates potion examples, adds examples for splash potions.

The documentation might change depending on weather this gets merged, which I will update once this is dealt with.
https://github.com/PGMDev/PGM/pull/715

Since the potion pull request was closed, could we take another look at this PR? None of the current changes mention anything added in that pull request

Since the potion pull request was closed, could we take another look at this PR? None of the current changes mention anything added in that pull request

Thought this PR documented https://github.com/PGMDev/PGM/pull/715, my bad. Will take a look this afternoon 👍

Thought this PR documented https://github.com/PGMDev/PGM/pull/715, my bad. Will take a look this afternoon 👍

Thanks for contributing!

authors: CoWinkKeyDinkInc Indicardo

repo: PGMDev/Website


text:
Tweek Image Re-sizing

Make sure images are re-sizing properly

Users can now modify their own settings for better options.

repo: PHCNetworks/phc-press


text:
Added possibility to disable a SetupTrigger

Configuring SetupTriggers can sometimes be hard and while development it could be necessary to disable a trigger. Instead of removing it from configuration, I added a property to disable it.
This must be evaluated in the implementation of the module or within the SetupTriggerBase. I currently have no idea which is the right place.

Is it sufficient if disable takes effect after module restart?
In that case I suggest the module implements it, that would be consistent with other module-plugin relationships. Especially since triggers are not aware of the context of the evaluation and the current system state.

authors: Toxantron dbeuchler

repo: PHOENIXCONTACT/MORYX-Factory


text:
add CMakeLists.txt

添加CMakeLists.txt，支持使用cmake编译，主要是修改了某些类的参数初始化列表的初始化顺序，以解决使用cmake编译产生的reorder警告
修改Logger.h里的_DEBUG宏为XOP_DEBUG宏，解决LOG_DEBUG未定义的bug

windows下编译cmakeList需要添加target_link_libraries(rtp_h264_file xop net pthread ws2_32 iphlpapi)

authors: gerryhjs ouweibin


text:
Feat/item acervo firebase

Feature feat/item-acervo-firebas
Resolve
#136
Descrição
Muda o comportamento dos métodos de CRUD
Adições
Método de mover item de coleção
Alterações
Refências usadas nos métodos de CRUD
Verificando
Desenvolvedor

Funcionamento dos métodos de CRUD

Revisor

[ ] Funcionalidade verificada localmente

const [file, setFile] = useState<File | null>(null);
const handleFileChange = (event: React.ChangeEvent) => {
if (event.target.files && event.target.files.length > 0) {
setFile(event.target.files[0]);
}
};
const handleButtonClick = async () => {
if (!file) {
console.error("No file selected");
return;
}
const newItem = {
  dataDoacao: new Date(),
  nome: "Item domestico",
  descricao: "Descrição",
  colecao: "Item domestico",
  curiosidades: "Curiosidades",
  privado: true,
  imagens: [{
    title: file.name,
    alt: "Imagem",
    src: file
  } as unknown as Imagem]
} as unknown as ItemAcervo;

await methodsItemAcervo.adicionarItemAcervo(
  newItem,
  {
    id: "colecoes/privado/lista/Fotografia",
    nome: "Fotografia",
    privado: false,
  } as Colecao
);

};
const editarArquivo = async () => {
if (!file) {
console.error("No file selected");
return;
}
const newItem = {
  dataDoacao: new Date(),
  descricao: "Descrição",
  colecao: "Item doméstico",
  nome: "Nome",
  curiosidades: "Curiosidades",
  privado: false,
  imagens: [{
    title: file.name,
    alt: "Imagem",
    src: file
  }] as Array<Imagem>
} as unknown as ItemAcervo;

await methodsItemAcervo.updateItemAcervo(
  newItem,
  "colecoes/privado/lista/Fotografia/itens/DlzTWn5Q2pKuF5M4HO8q",
  {
    id: "colecoes/privado/lista/Fotografia",
    nome: "Fotografia",
    privado: false,
  } as Colecao
);
COLOCAR DENTRO DO RETURN
<div style={{ padding: "20px" }}>
  <input type="file" id="file" onChange={handleFileChange} />
  <button onClick={handleButtonClick}>Adicionar</button>
  <button onClick={editarArquivo}>Editar</button>
</div>

}
Código de testes da Home.tsx


text:
Missing option to select user store

Issue description
The crated certifictae is located within the Admin's store (no surprise as the wacs runs as admin). But for my application a user's store would be more appropriate because the application does not require to run as admin.
Am I missing an obvious setting to achieve this?
Steps to reproduce
Running the script

wacs --target manual --webroot webroot --verbose --store certificatestore --host foo.de --emailaddress wacsFoo@ca3s.org --accepttos --baseuri http://localhost:8080/acme/wacs/directory

as an arbitrary user create the cert in the admins store. That's not what's intended.
Client version: v2.0.5.246
Windows version:  Microsoft Windows [Version 10.0.17763.437]
Relevant part of log file:

Actually the program adds certificates to the computer store, which makes them available to all users that have sufficient privileges to the target store.
Adding the certificate to a user store poses some difficulties because as far as I know the .NET API only allows us to add them to the current user store (i.e. the user starting wacs.exe) which might be a specific user (though it has to be an administrator) on first-time creation, but will be SYSTEM for the scheduled task.
In theory it's possible to run separate scheduled tasks under different users accounts, but I think it's more of a hassle than having different users certificates together in the machine store.

Closing this, because I just don't think it's possible right now. Might be an interesting case when we do #992

authors: WouterTinus kuehne-trustable-de

repo: PKISharp/win-acme


text:
new-selfsignedcertificateex : Exception calling "Build" with "1" argument(s): "Cannot find the certificate and private key for decryption."

Tried on Win 10 / Server 2016, all with PS5.1
I’m retrieving our in-house CA cert with
$sc = get-item Cert:\CurrentUser\ca\8CD9F4687EACECE660B6D7F5919EBC436FE433B9
But when I attempt to use that signing cert with a new cert request as
new-selfsignedcertificateex -keyspec Signature -subject "cn=mach01.domain.com" -EnhancedKeyUsage "Server Authentication","Client Authentication" -KeyLength 2048 -issuer $sc
this error pops:
new-selfsignedcertificateex : Exception calling "Build" with "1" argument(s): "Cannot find the certificate and private key for decryption.
It seems that the private key from the signing cert isn’t available. I’m not sure if that’s a problem with our signing cert or just the way I’m trying to use it.

Does your certificate has associated private key? Say, when you open the certificate in Certifificates MMC, do you see that private key is there?

If I look at the Details pane on the signing cert, I don’t see a private key. Is that where I should see it?
Jay Meerdink
Database Administrator IV
ConServe
An ACA International PPMS Certified Agency
A Business Ethics Award Recipient
P: (585) 421-1000 ext. 3205
F: (585) 421-1028
From: Vadims Podans notifications@github.com
Sent: Tuesday, April 07, 2020 12:28 PM
To: PKISolutions/PSPKI PSPKI@noreply.github.com
Cc: Meerdink, Jay jmeerdink@conserve-arm.com; Author author@noreply.github.com
Subject: Re: [PKISolutions/PSPKI] new-selfsignedcertificateex : Exception calling "Build" with "1" argument(s): "Cannot find the certificate and private key for decryption." (#99)
Does your certificate has associated private key? Say, when you open the certificate in Certifificates MMC, do you see that private key is there?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/PKISolutions/PSPKI/issues/99#issuecomment-610488423, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM6F4HJHI2CWASQWDIONIU3RLNICDANCNFSM4MDHL2YA.

It is on General tab, at the bottom. You should see something like this:

No – that message isn’t on that cert.
Jay Meerdink
Database Administrator IV
ConServe
An ACA International PPMS Certified Agency
A Business Ethics Award Recipient
P: (585) 421-1000 ext. 3205
F: (585) 421-1028
From: Vadims Podans notifications@github.com
Sent: Tuesday, April 07, 2020 1:46 PM
To: PKISolutions/PSPKI PSPKI@noreply.github.com
Cc: Meerdink, Jay jmeerdink@conserve-arm.com; Author author@noreply.github.com
Subject: Re: [PKISolutions/PSPKI] new-selfsignedcertificateex : Exception calling "Build" with "1" argument(s): "Cannot find the certificate and private key for decryption." (#99)
It is on General tab, at the bottom. You should see something like this:
[image]https://user-images.githubusercontent.com/6384119/78702086-b61ccd80-7910-11ea-9a01-1c587e601028.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/PKISolutions/PSPKI/issues/99#issuecomment-610528451, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM6F4HLDGWEQ3PNGVWR3DKTRLNRGHANCNFSM4MDHL2YA.

Then you cannot use this certificate to sign other certificates, because signing requires private key.

OK – I was confused between validating the cert through the chain, and using the cert to sign.
Thank you!
Jay Meerdink
Database Administrator IV
ConServe
An ACA International PPMS Certified Agency
A Business Ethics Award Recipient
P: (585) 421-1000 ext. 3205
F: (585) 421-1028
From: Vadims Podans notifications@github.com
Sent: Tuesday, April 07, 2020 2:29 PM
To: PKISolutions/PSPKI PSPKI@noreply.github.com
Cc: Meerdink, Jay jmeerdink@conserve-arm.com; Author author@noreply.github.com
Subject: Re: [PKISolutions/PSPKI] new-selfsignedcertificateex : Exception calling "Build" with "1" argument(s): "Cannot find the certificate and private key for decryption." (#99)
Then you cannot use this certificate to sign other certificates, because signing requires private key.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/PKISolutions/PSPKI/issues/99#issuecomment-610549291, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM6F4HJNH45MXVBJRG2UHLLRLNWIBANCNFSM4MDHL2YA.

yes, these are two different and almost unrelated things.

repo: PKISolutions/PSPKI

license: MS-PL


text:
Upload media from HTTP source

Hello, would like to know if it is supported to upload a media (image JPG for example) directly using an http URL.
Like the URL returned from on OpenSea API:
https://lh3.googleusercontent.com/4VfZOC8OThInrab3_uxxchH3izmjRqMNFSoxZ5d7LuGBOj0mfa8-4nGopFwHQJkcktfet5Z_Vnc5LIQaGO8N30sBRF0aV3yNH0QapLI
Thank you
Camillo

Hi,
No, this isn't planned, as you can do it by yourself.
This can be something like this:
import * as https from 'https';
const url = 'https://lh3.googleusercontent.com/4VfZOC8OThInrab3_uxxchH3izmjRqMNFSoxZ5d7LuGBOj0mfa8-4nGopFwHQJkcktfet5Z_Vnc5LIQaGO8N30sBRF0aV3yNH0QapLI';

const binaryData = await new Promise((resolve, reject) => {
  https.get(url, res => {
    res.setEncoding('binary');
    let data = Buffer.alloc(0);

    res.on('data', (chunk) => {
      data = Buffer.concat(data, Buffer.from(chunk, 'binary'));
    });
    res.on('end', () => { resolve(data) });
  })
    .on('error', e => {
      reject(e);
    });
});

// use your downloaded image
const mediaId = await client.v1.uploadMedia(binaryData, { type: 'jpg' })


text:
unify logging

We didn't establish a clear policy around logging early on, so now some parts of muon use Scanpy's logger, while others issue plain warnings using the warnings module. Ideally, this should be unified, one way or another.

There are at least these options to consider, I assume:

built-in Python logging,
scanpy logging, configurable through scanpy.settings.verbosity,
re-using scanpy logging internals but make it configurable through [muon.set_options],(https://github.com/PMBio/muon/blob/master/muon/_core/config.py).

I would lean towards the last option since I would not expect scanpy.settings.verbosity to affect another package and I would also expect to be able to tune it separately if needed. I can expect it would frequently mean defining verbosity options across two lines instead of a single line of code but it seems to me more explicit and hence better.
Any thoughts?

authors: gtca ilia-kats

repo: PMBio/muon


text:
Questions about soilpsi code

Hi @rabramoff @email-clm
See below for a few questions about soilpsi, at your convenience, as I'd like to add some explanatory comments to the code if possible. I've prefixed with line numbers for easy reference.
 849 	om_sucsat = 10.3_r8    	! saturated suction for organic matter (Lets, 2000)
 850 	smpmin = -1._r8    	! restriction for min of soil potential line 750 of iniTimeConst.F90

What does iniTimeConst.F90 refer to?

 851 	organic_max = 130._r8
 852 	om_b = 2.7_r8

What's om_b? Where does this value come from?

 858 	om_frac = min(organic / organic_max, 1._r8)
 859 	sucsat = 10. * ( 10.**(1.88-0.0131*sand) )
 860 	bsw = (1.-om_frac)*(2.91 + 0.159*clay) + om_frac*om_b

What's bsw and is there a reference for these two equations?

 861 	sucsat = (1.-om_frac)*sucsat + om_sucsat*om_frac
 862 	s_node = min(1.0, max(vwc / vwcsat, 0.01))
 863 	smp = max(smpmin, (-sucsat * (s_node ** (-bsw))))
 864 	smp_l = smp
 865 	bsw2 = -(3.1 + 0.157 * clay - 0.003 * sand)
 866 	psisat = -(exp((1.54 - 0.0095*sand + 0.0063*(100.0-sand-clay))*log(10.0))*9.8e-5_r8)

If sand, silt, and clay are fractions (see #1 ) why are they being subtracted from 100 here?
Is there a citation for this equation?

Thanks!

Let me check, will get back to you shortly.
Xiaofeng
On Wed, Mar 6, 2019 at 4:10 PM Ben Bond-Lamberty notifications@github.com
wrote:

Hi @rabramoff https://github.com/rabramoff @email-clm
https://github.com/email-clm
See below for a few questions about soilpsi, at your convenience, as I'd
like to add some explanatory comments to the code if possible. I've
prefixed with line numbers for easy reference.
849 	om_sucsat = 10.3_r8    	! saturated suction for organic matter (Lets, 2000)
850 	smpmin = -1._r8    	! restriction for min of soil potential line 750 of iniTimeConst.F90

What does iniTimeConst.F90 refer to?

851 	organic_max = 130._r8
852 	om_b = 2.7_r8

What's om_b? Where does this value come from?

858 	om_frac = min(organic / organic_max, 1._r8)
859 	sucsat = 10. * ( 10.**(1.88-0.0131sand) )
860 	bsw = (1.-om_frac)(2.91 + 0.159clay) + om_fracom_b

What's bsw and is there a reference for these two equations?

861 	sucsat = (1.-om_frac)sucsat + om_sucsatom_frac
862 	s_node = min(1.0, max(vwc / vwcsat, 0.01))
863 	smp = max(smpmin, (-sucsat * (s_node ** (-bsw))))
864 	smp_l = smp
865 	bsw2 = -(3.1 + 0.157 * clay - 0.003 * sand)
866 	psisat = -(exp((1.54 - 0.0095sand + 0.0063(100.0-sand-clay))*log(10.0))*9.8e-5_r8)

If sand, silt, and clay are fractions (see #1
https://github.com/PNNL-TES/millenial/issues/1 ) why are they being
subtracted from 100 here?
Is there a citation for this equation?

Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PNNL-TES/millenial/issues/5, or mute the thread
https://github.com/notifications/unsubscribe-auth/AORC80i0nwWdHjAMA2j2QNuU63ahAjC_ks5vUFjsgaJpZM4biFLg
.

Sorry the unit for sand, silt, clay is percentage (0-100%).
The original functions for soil water potential are from CLM. Since the CLM
needs to refer to many other functions, the Millennial model has similar
but not exactly same variable names.
that is why you see some codes refer to iniTimeConst.F90 in CLM. Many
variables have been assigned a value, rather than directly read
iniTimeConst.F90 file (since we do not have that file in this model).
om_b is a Clapp Hornberger paramater for oragnic soil (Letts, 2000)
bsw is Clapp and Hornberger "b"
the calculation for soil hydraulic properties are from below reference, I
briefly read them in 2012 when I was in ORNL.
https://agupubs.onlinelibrary.wiley.com/doi/10.1029/WR014i004p00601
If you are able to access CLM code, you can find detailed there, the
variable names are not exactly same.
Otherwise, you can access those codes at
https://github.com/email-clm/clm-microbe/blob/6cb5c2c989e19797ad8f6c5b095eb5f45900850d/models/lnd/clm/src/clm4_5/main/iniTimeConst.F90.
this repo holds the model code revised in my lab. My lab added a microbial
module (bacteria/fungi/DOM) and microbial functional group-based CH4 module
into CLM. But did not change any code for the soil hydraulic. Hydrology was
changed little as well.
Best,
Xiaofeng
On Wed, Mar 6, 2019 at 4:16 PM Xiaofeng Xu notifications@github.com wrote:

Let me check, will get back to you shortly.
Xiaofeng
On Wed, Mar 6, 2019 at 4:10 PM Ben Bond-Lamberty <notifications@github.com

wrote:

Hi @rabramoff https://github.com/rabramoff @email-clm
https://github.com/email-clm
See below for a few questions about soilpsi, at your convenience, as I'd
like to add some explanatory comments to the code if possible. I've
prefixed with line numbers for easy reference.
849 om_sucsat = 10.3_r8 ! saturated suction for organic matter (Lets,

850 smpmin = -1._r8 ! restriction for min of soil potential line 750 of
iniTimeConst.F90

What does iniTimeConst.F90 refer to?

851 organic_max = 130._r8
852 om_b = 2.7_r8

What's om_b? Where does this value come from?

858 om_frac = min(organic / organic_max, 1._r8)
859 sucsat = 10. * ( 10.**(1.88-0.0131sand) )
860 bsw = (1.-om_frac)(2.91 + 0.159clay) + om_fracom_b

What's bsw and is there a reference for these two equations?

861 sucsat = (1.-om_frac)sucsat + om_sucsatom_frac
862 s_node = min(1.0, max(vwc / vwcsat, 0.01))
863 smp = max(smpmin, (-sucsat * (s_node ** (-bsw))))
864 smp_l = smp
865 bsw2 = -(3.1 + 0.157 * clay - 0.003 * sand)
866 psisat = -(exp((1.54 - 0.0095sand +
0.0063(100.0-sand-clay))*log(10.0))*9.8e-5_r8)

If sand, silt, and clay are fractions (see #1
https://github.com/PNNL-TES/millenial/issues/1 ) why are they being
subtracted from 100 here?
Is there a citation for this equation?

Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PNNL-TES/millenial/issues/5, or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AORC80i0nwWdHjAMA2j2QNuU63ahAjC_ks5vUFjsgaJpZM4biFLg
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PNNL-TES/millenial/issues/5#issuecomment-470329751,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AORC8_wU2pTBlPN2om_0xFaIdq6ycbNIks5vUFpAgaJpZM4biFLg
.

That's fantastic–thank you.

authors: bpbond email-clm

repo: PNNL-TES/millenial


text:
Rounder border around the cards

In figma we used 32deg round corners. I like that level of roundness if possible

@dasaderi updated on dev site! https://prereview-dev.azurewebsites.net/

Hi @dasaderi is this one good to go? If so please close out, if not please let me know!

authors: dasaderi rudietuesdays

repo: PREreview/prereview


text:
MS2: Property Panel Improvements

Summary
Design Improvements for Property Panel, Store values in Property Panel in Backend
Details

Property Panel as collapsable and resizable card
store values for color, milestones, custom properties in backend
show name and type of element in general info of property panel
remove scrollbars in navigation sider and main view

@LucasMGo @FelipeTrost What's the status on this PR?

@LucasMGo @FelipeTrost What's the status on this PR?

I addressed most of the requested changes by now. The only thing I couldn't fix was the jittering of the property panel when it is opened. I couldn't really figure out why that happens. Maybe I can fix that in a separate PR later.

authors: LucasMGo OhKai

repo: PROCEED-Labs/proceed


text:
Sitemap links pointing to the wrong base URL

Story link URLs in the sitemap have a base URL of sitemap.theworld.org URL and not the base URL: https://sitemap.theworld.org/wp-sitemap-posts-post-1.xml

Adding to Four Kitchens Queue

Fixed in #216


text:
New command to get the used config for a scenario

New command Get-BicepNetConfig, closes #34
Dependency script change to allow for preview versions of .NET
Version bump

See if Get-BicepNetConfig matches the expectations. It needs a path, and returns an object with two properties:

Path - The path to the .bicep file to use for finding the config to use, or "Default" if no bicepconfig.json was found.
Config - The contents of the configuration. Not sure if we want to expose this for the user (Bicep CLI specifically has a comment in their version of the file regarding this), and if we do we should maybe consider returning the "fully merged" configuration if the user has only provided a partial config file (such as only specified the module registry parts).

and if we do we should maybe consider returning the "fully merged" configuration if the user has only provided a partial config file (such as only specified the module registry parts).

I like the idea of returning the fully merged config. It makes sense to show the current config.

Works great! Is it stupid to add a -Default switch? At least I would like to have the option to get the default config in a simple way.

Have a look at the changes now! I added a -Default switch, which is not mandatory (so you can run just Get-BicepNetConfig on its own), and the output is now merged with the default config, so you always see the full configuration of your command.

After offline discussions:

Add -Scope parameter with local, default and merged  as allowed values

The -Default parameter is now replaced by -Scope which allows three different values.

Default - Gets the built-in configuration.
Merged - Combines any found configuration file with the built-in configuration.
Local - Gets only the configuration from a found configuration file.

Running only Get-BicepNetConfig will set the scope to Default. Running Get-BicepNetConfig with the -Path parameter will set the scope to Merged.

authors: PalmEmanuel StefanIvemo

repo: PSBicep/BicepNet


text:
TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/112026

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/112935

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/114060

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/116651


text:
"make posix_sitl_default gazebo" error

Hi,
I cloned the PX4 Firmware v1.7.3.
I am able to launch the jmavsim simulator with the command "make posix_sitl_default jmavsim" and it works fine.
If I run gazebo it's working fine on its own.
My gazebo version is Gazebo9 and I m working on ubuntu 16.04LTS
But when I run the command "make posix_sitl_default gazebo" I get the following error log:
[1/1] Re-running CMake...
-- Build Type: RelWithDebInfo
-- PX4 VERSION: v1.7.3
-- CONFIG: posix_sitl_default
-- Build Type: RelWithDebInfo
-- C compiler: cc (Ubuntu 5.4.0-6ubuntu116.04.9) 5.4.0 20160609
-- C++ compiler: c++ (Ubuntu 5.4.0-6ubuntu116.04.9) 5.4.0 20160609
-- Configuring done
-- Generating done
-- Build files have been written to: /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/build/posix_sitl_default
[7/18] Performing configure step for 'sitl_gazebo'
-- install-prefix: /usr/local
-- Boost version: 1.58.0
-- Found the following Boost libraries:
-- thread
-- signals
-- system
-- filesystem
-- program_options
-- regex
-- iostreams
-- date_time
-- chrono
-- atomic
-- Boost version: 1.58.0
-- Looking for OGRE...
-- Found Ogre Ghadamon (1.9.0)
-- Found OGRE: optimized;/usr/lib/x86_64-linux-gnu/libOgreMain.so;debug;/usr/lib/x86_64-linux-gnu/libOgreMain.so
-- Looking for OGRE_Paging...
-- Found OGRE_Paging: optimized;/usr/lib/x86_64-linux-gnu/libOgrePaging.so;debug;/usr/lib/x86_64-linux-gnu/libOgrePaging.so
-- Looking for OGRE_Terrain...
-- Found OGRE_Terrain: optimized;/usr/lib/x86_64-linux-gnu/libOgreTerrain.so;debug;/usr/lib/x86_64-linux-gnu/libOgreTerrain.so
-- Looking for OGRE_Property...
-- Found OGRE_Property: optimized;/usr/lib/x86_64-linux-gnu/libOgreProperty.so;debug;/usr/lib/x86_64-linux-gnu/libOgreProperty.so
-- Looking for OGRE_RTShaderSystem...
-- Found OGRE_RTShaderSystem: optimized;/usr/lib/x86_64-linux-gnu/libOgreRTShaderSystem.so;debug;/usr/lib/x86_64-linux-gnu/libOgreRTShaderSystem.so
-- Looking for OGRE_Volume...
-- Found OGRE_Volume: optimized;/usr/lib/x86_64-linux-gnu/libOgreVolume.so;debug;/usr/lib/x86_64-linux-gnu/libOgreVolume.so
-- Looking for OGRE_Overlay...
-- Found OGRE_Overlay: optimized;/usr/lib/x86_64-linux-gnu/libOgreOverlay.so;debug;/usr/lib/x86_64-linux-gnu/libOgreOverlay.so
-- Found Protobuf: /usr/lib/x86_64-linux-gnu/libprotobuf.so (Required is at least version "2.3.0")
-- Config-file not installed for ZeroMQ -- checking for pkg-config
-- Checking for module 'libzmq >= 4'
-- Found libzmq , version 4.1.4
-- Checking for module 'uuid'
-- Found uuid, version 2.27.0
-- Checking for module 'tinyxml2'
-- Found tinyxml2, version 2.2.0
-- Looking for dlfcn.h - found
-- Looking for libdl - found
-- FreeImage.pc not found, we will search for FreeImage_INCLUDE_DIRS and FreeImage_LIBRARIES
-- Checking for module 'gts'
-- Found gts, version 0.7.6
-- Checking for module 'libswscale'
-- Found libswscale, version 3.1.101
-- Checking for module 'libavdevice >= 56.4.100'
-- Found libavdevice , version 56.4.100
-- Checking for module 'libavformat'
-- Found libavformat, version 56.40.101
-- Checking for module 'libavcodec'
-- Found libavcodec, version 56.60.100
-- Checking for module 'libavutil'
-- Found libavutil, version 54.31.100
-- Checking for module 'jsoncpp'
-- Found jsoncpp, version 1.7.2
-- Checking for module 'yaml-0.1'
-- Found yaml-0.1, version 0.1.6
-- Checking for module 'libzip'
-- Found libzip, version 1.0.1
-- Boost version: 1.58.0
-- Found the following Boost libraries:
-- system
-- thread
-- timer
-- chrono
-- date_time
-- atomic
-- Building klt_feature_tracker without catkin
-- Building OpticalFlow with OpenCV
-- catkin DISABLED
-- Found Protobuf: /usr/lib/x86_64-linux-gnu/libprotobuf.so
Gazebo version: 9.0
-- Boost version: 1.58.0
-- Found the following Boost libraries:
-- system
-- thread
-- timer
-- chrono
-- date_time
-- atomic
-- Configuring done
-- Generating done
-- Build files have been written to: /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/build/posix_sitl_default/build_gazebo
[15/18] Performing build step for 'sitl_gazebo'
FAILED: cd /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/build/posix_sitl_default/build_gazebo && /usr/bin/cmake --build . && /usr/bin/cmake -E touch /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/build/posix_sitl_default/external/Stamp/sitl_gazebo/sitl_gazebo-build
[1/25] Building CXX object CMakeFiles/gazebo_lidar_plugin.dir/src/gazebo_lidar_plugin.cpp.o
[2/25] Building CXX object CMakeFiles/rotors_gazebo_multirotor_base_plugin.dir/src/gazebo_multirotor_base_plugin.cpp.o
[3/25] Building CXX object CMakeFiles/rotors_gazebo_mavlink_interface.dir/src/gazebo_mavlink_interface.cpp.o
[4/25] Building CXX object CMakeFiles/rotors_gazebo_imu_plugin.dir/src/gazebo_imu_plugin.cpp.o
[5/25] Building CXX object CMakeFiles/rotors_gazebo_controller_interface.dir/src/gazebo_controller_interface.cpp.o
[6/25] Building CXX object CMakeFiles/rotors_gazebo_gimbal_controller_plugin.dir/src/gazebo_gimbal_controller_plugin.cpp.o
FAILED: /usr/bin/c++ -DLIBBULLET_VERSION=2.83 -DLIBBULLET_VERSION_GT_282 -Drotors_gazebo_mavlink_interface_EXPORTS -I/usr/include/opencv -isystem /usr/include/gazebo-9 -isystem /usr/include/bullet -isystem /usr/include/simbody -isystem /usr/include/sdformat-6.0 -isystem /usr/include/ignition/math4 -isystem /usr/include/OGRE -isystem /usr/include/OGRE/Terrain -isystem /usr/include/OGRE/Paging -isystem /usr/include/ignition/transport4 -isystem /usr/include/ignition/msgs1 -isystem /usr/include/ignition/common1 -isystem /usr/include/ignition/fuel_tools1 -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/external/OpticalFlow/include -I/usr/include/gazebo-9/gazebo/msgs -I/usr/include/eigen3 -I. -I/usr/include/eigen3/eigen3 -I/usr/local/include/OGRE -I/usr/local/include/OGRE/Paging -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/mavlink/include -isystem /usr/include/uuid -isystem /usr/include/x86_64-linux-gnu -std=c++11 -std=c++11 -Wno-deprecated-declarations -fPIC -I/usr/include/uuid -I/usr/include/x86_64-linux-gnu -std=gnu++14 -MMD -MT CMakeFiles/rotors_gazebo_mavlink_interface.dir/src/gazebo_mavlink_interface.cpp.o -MF CMakeFiles/rotors_gazebo_mavlink_interface.dir/src/gazebo_mavlink_interface.cpp.o.d -o CMakeFiles/rotors_gazebo_mavlink_interface.dir/src/gazebo_mavlink_interface.cpp.o -c /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_mavlink_interface.cpp
In file included from /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_mavlink_interface.cpp:22:0:
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include/gazebo_mavlink_interface.h:35:34: fatal error: gazebo/math/Vector3.hh: No such file or directory
compilation terminated.
FAILED: /usr/bin/c++ -DLIBBULLET_VERSION=2.83 -DLIBBULLET_VERSION_GT_282 -Drotors_gazebo_multirotor_base_plugin_EXPORTS -I/usr/include/opencv -isystem /usr/include/gazebo-9 -isystem /usr/include/bullet -isystem /usr/include/simbody -isystem /usr/include/sdformat-6.0 -isystem /usr/include/ignition/math4 -isystem /usr/include/OGRE -isystem /usr/include/OGRE/Terrain -isystem /usr/include/OGRE/Paging -isystem /usr/include/ignition/transport4 -isystem /usr/include/ignition/msgs1 -isystem /usr/include/ignition/common1 -isystem /usr/include/ignition/fuel_tools1 -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/external/OpticalFlow/include -I/usr/include/gazebo-9/gazebo/msgs -I/usr/include/eigen3 -I. -I/usr/include/eigen3/eigen3 -I/usr/local/include/OGRE -I/usr/local/include/OGRE/Paging -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/mavlink/include -isystem /usr/include/uuid -isystem /usr/include/x86_64-linux-gnu -std=c++11 -std=c++11 -Wno-deprecated-declarations -fPIC -I/usr/include/uuid -I/usr/include/x86_64-linux-gnu -std=gnu++14 -MMD -MT CMakeFiles/rotors_gazebo_multirotor_base_plugin.dir/src/gazebo_multirotor_base_plugin.cpp.o -MF CMakeFiles/rotors_gazebo_multirotor_base_plugin.dir/src/gazebo_multirotor_base_plugin.cpp.o.d -o CMakeFiles/rotors_gazebo_multirotor_base_plugin.dir/src/gazebo_multirotor_base_plugin.cpp.o -c /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_multirotor_base_plugin.cpp
In file included from /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_multirotor_base_plugin.cpp:21:0:
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include/gazebo_multirotor_base_plugin.h:31:34: fatal error: gazebo/math/Vector3.hh: No such file or directory
compilation terminated.
FAILED: /usr/bin/c++ -DLIBBULLET_VERSION=2.83 -DLIBBULLET_VERSION_GT_282 -Drotors_gazebo_gimbal_controller_plugin_EXPORTS -I/usr/include/opencv -isystem /usr/include/gazebo-9 -isystem /usr/include/bullet -isystem /usr/include/simbody -isystem /usr/include/sdformat-6.0 -isystem /usr/include/ignition/math4 -isystem /usr/include/OGRE -isystem /usr/include/OGRE/Terrain -isystem /usr/include/OGRE/Paging -isystem /usr/include/ignition/transport4 -isystem /usr/include/ignition/msgs1 -isystem /usr/include/ignition/common1 -isystem /usr/include/ignition/fuel_tools1 -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/external/OpticalFlow/include -I/usr/include/gazebo-9/gazebo/msgs -I/usr/include/eigen3 -I. -I/usr/include/eigen3/eigen3 -I/usr/local/include/OGRE -I/usr/local/include/OGRE/Paging -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/mavlink/include -isystem /usr/include/uuid -isystem /usr/include/x86_64-linux-gnu -std=c++11 -std=c++11 -Wno-deprecated-declarations -fPIC -I/usr/include/uuid -I/usr/include/x86_64-linux-gnu -std=gnu++14 -MMD -MT CMakeFiles/rotors_gazebo_gimbal_controller_plugin.dir/src/gazebo_gimbal_controller_plugin.cpp.o -MF CMakeFiles/rotors_gazebo_gimbal_controller_plugin.dir/src/gazebo_gimbal_controller_plugin.cpp.o.d -o CMakeFiles/rotors_gazebo_gimbal_controller_plugin.dir/src/gazebo_gimbal_controller_plugin.cpp.o -c /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp: In member function ‘virtual void gazebo::GimbalControllerPlugin::Init()’:
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:139:45: error: ‘class gazebo::physics::World’ has no member named ‘GetName’
this->node->Init(this->model->GetWorld()->GetName());
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:141:51: error: ‘class gazebo::physics::World’ has no member named ‘GetSimTime’
this->lastUpdateTime = this->model->GetWorld()->GetSimTime();
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp: In member function ‘void gazebo::GimbalControllerPlugin::OnUpdate()’:
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:283:48: error: ‘class gazebo::physics::World’ has no member named ‘GetSimTime’
common::Time time = this->model->GetWorld()->GetSimTime();
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:306:29: error: ‘class gazebo::physics::Joint’ has no member named ‘GetUpperLimit’
rDirthis->rollJoint->GetUpperLimit(0).Radian(),
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:307:26: error: ‘class gazebo::physics::Joint’ has no member named ‘GetLowerLimit’
rDirthis->rollJoint->GetLowerLimit(0).Radian());
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:309:30: error: ‘class gazebo::physics::Joint’ has no member named ‘GetUpperLimit’
pDirthis->pitchJoint->GetUpperLimit(0).Radian(),
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:310:30: error: ‘class gazebo::physics::Joint’ has no member named ‘GetLowerLimit’
pDirthis->pitchJoint->GetLowerLimit(0).Radian());
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:312:28: error: ‘class gazebo::physics::Joint’ has no member named ‘GetLowerLimit’
yDirthis->yawJoint->GetLowerLimit(0).Radian(),
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:313:25: error: ‘class gazebo::physics::Joint’ has no member named ‘GetUpperLimit’
yDirthis->yawJoint->GetUpperLimit(0).Radian());
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:331:31: error: ‘class gazebo::physics::Joint’ has no member named ‘GetLowerLimit’
(pDirthis->pitchJoint->GetLowerLimit(0).Radian(),
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:332:30: error: ‘class gazebo::physics::Joint’ has no member named ‘GetLowerLimit’
rDirthis->rollJoint->GetLowerLimit(0).Radian(),
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:333:29: error: ‘class gazebo::physics::Joint’ has no member named ‘GetLowerLimit’
yDirthis->yawJoint->GetLowerLimit(0).Radian());
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:335:31: error: ‘class gazebo::physics::Joint’ has no member named ‘GetUpperLimit’
(pDirthis->pitchJoint->GetUpperLimit(0).Radian(),
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:336:30: error: ‘class gazebo::physics::Joint’ has no member named ‘GetUpperLimit’
rDirthis->rollJoint->GetUpperLimit(0).Radian(),
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:337:29: error: ‘class gazebo::physics::Joint’ has no member named ‘GetUpperLimit’
yDirthis->yawJoint->GetUpperLimit(0).Radian());
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:436:29: error: ‘class gazebo::physics::Joint’ has no member named ‘GetAngle’
ss << this->pitchJoint->GetAngle(0).Radian();
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:440:28: error: ‘class gazebo::physics::Joint’ has no member named ‘GetAngle’
ss << this->rollJoint->GetAngle(0).Radian();
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_gimbal_controller_plugin.cpp:444:27: error: ‘class gazebo::physics::Joint’ has no member named ‘GetAngle’
ss << this->yawJoint->GetAngle(0).Radian();
^
FAILED: /usr/bin/c++ -DLIBBULLET_VERSION=2.83 -DLIBBULLET_VERSION_GT_282 -Dgazebo_lidar_plugin_EXPORTS -I/usr/include/opencv -isystem /usr/include/gazebo-9 -isystem /usr/include/bullet -isystem /usr/include/simbody -isystem /usr/include/sdformat-6.0 -isystem /usr/include/ignition/math4 -isystem /usr/include/OGRE -isystem /usr/include/OGRE/Terrain -isystem /usr/include/OGRE/Paging -isystem /usr/include/ignition/transport4 -isystem /usr/include/ignition/msgs1 -isystem /usr/include/ignition/common1 -isystem /usr/include/ignition/fuel_tools1 -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/external/OpticalFlow/include -I/usr/include/gazebo-9/gazebo/msgs -I/usr/include/eigen3 -I. -I/usr/include/eigen3/eigen3 -I/usr/local/include/OGRE -I/usr/local/include/OGRE/Paging -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/mavlink/include -isystem /usr/include/uuid -isystem /usr/include/x86_64-linux-gnu -std=c++11 -std=c++11 -Wno-deprecated-declarations -fPIC -I/usr/include/uuid -I/usr/include/x86_64-linux-gnu -std=gnu++14 -MMD -MT CMakeFiles/gazebo_lidar_plugin.dir/src/gazebo_lidar_plugin.cpp.o -MF CMakeFiles/gazebo_lidar_plugin.dir/src/gazebo_lidar_plugin.cpp.o.d -o CMakeFiles/gazebo_lidar_plugin.dir/src/gazebo_lidar_plugin.cpp.o -c /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_lidar_plugin.cpp
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_lidar_plugin.cpp: In destructor ‘virtual gazebo::RayPlugin::~RayPlugin()’:
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_lidar_plugin.cpp:54:37: error: ‘class gazebo::physics::MultiRayShape’ has no member named ‘DisconnectNewLaserScans’
this->parentSensor->LaserShape()->DisconnectNewLaserScans(
^
FAILED: /usr/bin/c++ -DLIBBULLET_VERSION=2.83 -DLIBBULLET_VERSION_GT_282 -Drotors_gazebo_controller_interface_EXPORTS -I/usr/include/opencv -isystem /usr/include/gazebo-9 -isystem /usr/include/bullet -isystem /usr/include/simbody -isystem /usr/include/sdformat-6.0 -isystem /usr/include/ignition/math4 -isystem /usr/include/OGRE -isystem /usr/include/OGRE/Terrain -isystem /usr/include/OGRE/Paging -isystem /usr/include/ignition/transport4 -isystem /usr/include/ignition/msgs1 -isystem /usr/include/ignition/common1 -isystem /usr/include/ignition/fuel_tools1 -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/external/OpticalFlow/include -I/usr/include/gazebo-9/gazebo/msgs -I/usr/include/eigen3 -I. -I/usr/include/eigen3/eigen3 -I/usr/local/include/OGRE -I/usr/local/include/OGRE/Paging -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/mavlink/include -isystem /usr/include/uuid -isystem /usr/include/x86_64-linux-gnu -std=c++11 -std=c++11 -Wno-deprecated-declarations -fPIC -I/usr/include/uuid -I/usr/include/x86_64-linux-gnu -std=gnu++14 -MMD -MT CMakeFiles/rotors_gazebo_controller_interface.dir/src/gazebo_controller_interface.cpp.o -MF CMakeFiles/rotors_gazebo_controller_interface.dir/src/gazebo_controller_interface.cpp.o.d -o CMakeFiles/rotors_gazebo_controller_interface.dir/src/gazebo_controller_interface.cpp.o -c /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_controller_interface.cpp
In file included from /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include/gazebo_controller_interface.h:35:0,
from /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_controller_interface.cpp:22:
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include/common.h:55:28: error: ‘math’ does not name a type
double GetDegrees360(const math::Angle& angle) {
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include/common.h:55:39: error: expected unqualified-id before ‘&’ token
double GetDegrees360(const math::Angle& angle) {
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include/common.h:55:39: error: expected ‘)’ before ‘&’ token
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include/common.h:55:41: error: expected initializer before ‘angle’
double GetDegrees360(const math::Angle& angle) {
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_controller_interface.cpp: In destructor ‘virtual gazebo::GazeboControllerInterface::~GazeboControllerInterface()’:
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_controller_interface.cpp:27:3: error: ‘DisconnectWorldUpdateBegin’ is not a member of ‘gazebo::event::Events’
event::Events::DisconnectWorldUpdateBegin(updateConnection_);
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_controller_interface.cpp: In member function ‘void gazebo::GazeboControllerInterface::OnUpdate(const gazebo::common::UpdateInfo&)’:
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_controller_interface.cpp:69:30: error: ‘class gazebo::physics::World’ has no member named ‘GetSimTime’
common::Time now = world_->GetSimTime();
^
FAILED: /usr/bin/c++ -DLIBBULLET_VERSION=2.83 -DLIBBULLET_VERSION_GT_282 -Drotors_gazebo_imu_plugin_EXPORTS -I/usr/include/opencv -isystem /usr/include/gazebo-9 -isystem /usr/include/bullet -isystem /usr/include/simbody -isystem /usr/include/sdformat-6.0 -isystem /usr/include/ignition/math4 -isystem /usr/include/OGRE -isystem /usr/include/OGRE/Terrain -isystem /usr/include/OGRE/Paging -isystem /usr/include/ignition/transport4 -isystem /usr/include/ignition/msgs1 -isystem /usr/include/ignition/common1 -isystem /usr/include/ignition/fuel_tools1 -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/external/OpticalFlow/include -I/usr/include/gazebo-9/gazebo/msgs -I/usr/include/eigen3 -I. -I/usr/include/eigen3/eigen3 -I/usr/local/include/OGRE -I/usr/local/include/OGRE/Paging -I/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/mavlink/include -isystem /usr/include/uuid -isystem /usr/include/x86_64-linux-gnu -std=c++11 -std=c++11 -Wno-deprecated-declarations -fPIC -I/usr/include/uuid -I/usr/include/x86_64-linux-gnu -std=gnu++14 -MMD -MT CMakeFiles/rotors_gazebo_imu_plugin.dir/src/gazebo_imu_plugin.cpp.o -MF CMakeFiles/rotors_gazebo_imu_plugin.dir/src/gazebo_imu_plugin.cpp.o.d -o CMakeFiles/rotors_gazebo_imu_plugin.dir/src/gazebo_imu_plugin.cpp.o -c /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp
In file included from /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include/gazebo_imu_plugin.h:32:0,
from /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp:21:
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include/common.h:55:28: error: ‘math’ does not name a type
double GetDegrees360(const math::Angle& angle) {
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include/common.h:55:39: error: expected unqualified-id before ‘&’ token
double GetDegrees360(const math::Angle& angle) {
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include/common.h:55:39: error: expected ‘)’ before ‘&’ token
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include/common.h:55:41: error: expected initializer before ‘angle’
double GetDegrees360(const math::Angle& angle) {
^
In file included from /home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp:21:0:
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include/gazebo_imu_plugin.h:140:3: error: ‘math’ does not name a type
math::Vector3 gravity_W_;
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/include/gazebo_imu_plugin.h:141:3: error: ‘math’ does not name a type
math::Vector3 velocity_prev_W_;
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp: In constructor ‘gazebo::GazeboImuPlugin::GazeboImuPlugin()’:
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp:34:7: error: class ‘gazebo::GazeboImuPlugin’ does not have any field named ‘velocity_prev_W_’
velocity_prev_W_(0,0,0)
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp: In destructor ‘virtual gazebo::GazeboImuPlugin::~GazeboImuPlugin()’:
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp:39:3: error: ‘DisconnectWorldUpdateBegin’ is not a member of ‘gazebo::event::Events’
event::Events::DisconnectWorldUpdateBegin(updateConnection_);
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp: In member function ‘virtual void gazebo::GazeboImuPlugin::Load(gazebo::physics::ModelPtr, sdf::ElementPtr)’:
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp:97:24: error: ‘class gazebo::physics::World’ has no member named ‘GetSimTime’
last_time_ = world_->GetSimTime();
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp:164:3: error: ‘gravity_W_’ was not declared in this scope
gravity_W_ = world_->GetPhysicsEngine()->GetGravity();
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp:164:24: error: ‘class gazebo::physics::World’ has no member named ‘GetPhysicsEngine’
gravity_W_ = world_->GetPhysicsEngine()->GetGravity();
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp: In member function ‘void gazebo::GazeboImuPlugin::OnUpdate(const gazebo::common::UpdateInfo&)’:
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp:241:40: error: ‘class gazebo::physics::World’ has no member named ‘GetSimTime’
common::Time current_time = world_->GetSimTime();
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp:246:3: error: ‘math’ has not been declared
math::Pose T_W_I = link_->GetWorldPose(); //TODO(burrimi): Check tf.
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp:247:3: error: ‘math’ has not been declared
math::Quaternion C_W_I = T_W_I.rot;
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp:251:22: error: ‘C_W_I’ was not declared in this scope
orientation->set_x(C_W_I.x);
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp:274:3: error: ‘math’ has not been declared
math::Vector3 acceleration_I = link_->GetRelativeLinearAccel() - C_W_I.RotateVectorReverse(gravity_W_);
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp:277:3: error: ‘math’ has not been declared
math::Vector3 angular_vel_I = link_->GetRelativeAngularVel();
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp:279:41: error: ‘acceleration_I’ was not declared in this scope
Eigen::Vector3d linear_acceleration_I(acceleration_I.x,
^
/home/alexcherpi/Documents/GIT_PolyDrones/polydrones_px4/Tools/sitl_gazebo/src/gazebo_imu_plugin.cpp:282:38: error: ‘angular_vel_I’ was not declared in this scope
Eigen::Vector3d angular_velocity_I(angular_vel_I.x,
^
ninja: build stopped: subcommand failed.
ninja: build stopped: subcommand failed.
Makefile:147: recipe for target 'posix_sitl_default' failed
make: *** [posix_sitl_default] Error 1
Do you know what's wrong ?

I solved my issue.
I removed gazebo using:
sudo apt-get remove '.gazebo.' '.sdformat.' '.ignition-math.' '.ignition-msgs.' '.ignition-transport.'
Then I installed ros-kinetic-desktop-full using:
sudo apt-get install ros-kinetic-desktop-full
Then I ran the bash script from px4 dev guide:
ubuntu_sim_ros_gazebo.sh
And then I was able to launch the px4-gazebo simulation:
make posix_sitl_ekf2 gazebo
Even if it s not the the ROS version. Now my gazebo version is Gazebo version 7.12.0 (before version 9) which maybe solved my issue.
And I am also able to launch px4-ros-gazebo simulation:
roslaunch px4 posix_sitl.launch

@hamishwillee Yeah the Gazebo version 9 comes with the script ubuntu_sim.sh you mentioned. Gazebo 7 comes with the ros version ubuntu_sim_ros_gazebo.sh. The issue with me (shown in the my previous comment in this issue) was with Gazebo 9. But maybe I an isolated case.

@alexcherpi Thank you. I suspect that the fixes that enabled support for Gazebo 9 came in after v1.7.3. I tested them on master.

authors: alexcherpi hamishwillee


text:
LL40LS & terrain estimation: Implement proper driver-specific filtering

Issue
See https://github.com/PX4/Firmware/issues/9843
Solution
Changes:

A driver-specific filtering that is based on datasheets and experiments with this sensor (based on the concept: "If you know the specific weaknesses of your device, why not filter it directly inside the device driver). What is implemented is described here, but essentially we are now looking at a) absolute peak strength b) relative peak strength (basically signal-to-noise) and c) the absolute measurement to detect bull**** data.

All distance sensors now have a signal_strength field. I know there is also a covariance field, but it seems like basically no other sensor is using this. Signal strength is also a different concept/metric than covariance (in my opinion it is a bit easier to determine signal strength than true covariance of the measurement), so i think it is good to have both.

@priseborough @dagar I changed this line, because before I put the "if" statement the distance data was just always forwarded to the EKF even if the device limits (i.e. min/max range) were exceeded. That did not seem right to me. Can you check this please?

Testing
The filtering was tested on the bench extensively. In contrast to before, I am now getting very clean distance data from the sensor up to 27m distance, i.e. every time that LL40LS messes up the driver detects that and sets signal strength to zero. The EKF then just does not use that data because of this line . I will flight test the whole PR today and give you further feedback.
@ryanjAA or anyone else using the LidarLite: It would be good if you could test this with your sensors (which are slightly different versions) too.
Note: I am not really a low-level driver guy, so any feedback on what I might have messed up in the driver is greatly appreciated.

Can you please attach a link to a test log for this PR. I will review tomorrow.

I am resisting putting in sensor type specific threshold checks into the estimator because this will end up with multiple checks to handle the failure mechanisms for different sensor types. My preference is that the validity of sensor specific metrics such as noise variance, S/N ratio, etc is not done by the EKF. The sensor driver has access to full rate data and where estimator agnostic validity checking using pre-filtered and down-sampled data is achievable, it should be done in the sensor driver.
I would prefer a validity flag and a sensor noise variance metric to assist with estimator tuning.

I am resisting putting in sensor type specific threshold checks into the estimator because this will end up with multiple checks to handle the failure mechanisms for different sensor types. My preference is that the validity of sensor specific metrics such as noise variance, S/N ratio, etc is not done by the EKF. The sensor driver has access to full rate data and where estimator agnostic validity checking using pre-filtered and down-sampled data is achievable, it should be done in the sensor driver.

I think we totally agree with this. My approach in this PR is that each distance sensor driver calculates a signal_strength (as you say, leveraging knowledge about the specific failure mechanisms that are know for this sensor), and the ekf2 then simply has to check whether signal_strength==0.

So why 0 and not some other threshold? Isn't that sensor specific? If not, then that means we are using the signal strength also as a a de-facto validity indicator and the uORB description should be updated to state that a value of zero indicates an invalid reading.

@priseborough Log file is here: https://review.px4.io/plot_app?log=2ffbb1b4-f70f-421c-bb2c-892ecb51d623
Quick description of what is going on there (fixed-wing plane, always hand-launched):

Fixed-wing plane, hand-launched, location has a relatively constant terrain altitude at ~538m +/-3m with only a single tree which could disturb the measurement, otherwise the terrain is very clean.
t=935...1954s: Four autolaunches+autolandings
t=1985...2384: Stabilized flight, always climbing to an altitude where the distance sensor does not deliver valid readings, and then quickly descending to an altitude where it does. This was done to see how fast the terrain estimate becomes valid.
t=2384... 2670: Some higher-altitude flight in a region where the LL40LS does not deliver valid data. In contrast, it delivers a lot of outliers there. I did this to test the outlier rejection inside the driver that i added. Seems to work really nicely.
Afterwards: Manual flight, landing.

Findings/Questions from my side:

Overall seems to work really nice. Terrain estimate seems mostly correct (some slight drift observed during launches). If you compare that to the problems i had with the "old" approach here, there is a huge difference:  The terrain estimate becomes valid quickly after the distance sensor shows less than 25m, which was not the case before (where the HAGL test ratio first had to slowly converged to <1). Also, when we are actually at >25m AGL (i.e. the max_distance limit of the range sensor), then the terrain altitude is not estimated at all, whereas without this approach (see the issue again) the terrain was still always estimated and actually set to ~aircraft_altitude.
One small potential issue: At t=1777s, the terrain estimation stops briefly before a takeoff. Do you know why?
Other small potential issue: I feel like htere is a slight delay (ca 1.5 seconds) between the distance sensor delivering its first measurement of <max_distance and the terrain estimate becoming valid. It's not a big deal, but i was wondering whether this is a general delay that could later on also influence when we flare (where a 1.5s delay would make a huge difference!). The range sensor time delay parameter is only set to 5ms, so that cannot be it. Do you have any clue?

So why 0 and not some other threshold? Isn't that sensor specific? If not, then that means we are using the signal strength also as a a de-facto validity indicator and the uORB description should be updated to state that a value of zero indicates an invalid reading.

I think it is clear that for any sensor, if signal_strength=0, then the signal is invalid. This is thus not sensor-specific. Also note that what is then actually considered invalid (i.e. signal strength = 0) is decided by the driver, i.e. ekf2 again does not have to deal with this. But sure, if you want i can add a brief comment that signal_strength=0 means invalid signal.

@philipoe Yes please do.  I would prefer the term 'quality' instead of 'signal strength' because there are some optical based techniques (eg stereo camera) where the concept of a return signal strength is not applicable.

@philipoe  Please pull in  this commit https://github.com/priseborough/Firmware/commit/3e0d1dfd7751b68f56527c2cb7384f7541429162 and we can close https://github.com/PX4/Firmware/pull/9886

@priseborough I merged the commit you mentioned. But this actually requires changes to a lot of distance sensor drivers because they all now have to set signal_quality=0 when range>range_max or range<range_min. Wouldn't it be easier to keep the range_max and range_min checks there in ekf2_main?

@philipoe The quality ==0 check this adds to ekf2_main prior to pushing data into the EKF is additional to the range checking that the ekf does internally, so we are not giving up anything we had before with those sensors.

Ok, great, hadn't seen that...

https://github.com/PX4/ecl/blob/master/EKF/control.cpp#L1152

I will give this a test on SITL at commit https://github.com/PX4/Firmware/pull/9865/commits/3e0d1dfd7751b68f56527c2cb7384f7541429162 but it would be good if someone with a LidarLite can also run a test.

The sonar data when running 'make posix gazebo_iris_opt_flow' is clipped such that it never exceeds max_distance and min_distance and therefore always passes checks. I will fix this in a separate PR. With the limits adjusted so that distance_sensor.distance can exceed the  distance_sensor.max_distance and distance_sensor.min_distance, the test works as expected.

https://logs.px4.io/plot_app?log=ff9d9030-9dd5-4f3d-88a7-eed28bb577e3

@philipoe, did you have a chance to test your changes and @priseborough's changes during a test-flight?
I just installed the Lidar-Lite v3 in our Wing Z-84 plane and I was going to test it tomorrow.  However, I currently have the v1.8.0 release installed in the PixRacer. Should I rebuild the firmware from master instead and test it?

@philipoe, did you have a chance to test your changes and @priseborough's changes during a test-flight?

Not yet, no. I did test this PR up to f94b976 however.

@philipoe Your issue #9843 seems to be more concerning about the autoland.  If that is the case, then the current LL40LS driver in the v.1.8.0 release should work fine as long as the plane is landed manually.  Is that correct?
BTW, do you also get a max_distance of 25m when you run the "ll40ls test" command from the shell?
According to the spec, the max should be up to 40m.

@philipoe Your issue #9843 seems to be more concerning about the autoland. If that is the case, then the current LL40LS driver in the v.1.8.0 release should work fine as long as the plane is landed manually. Is that correct?
It works fine in the sense that it delivers values. It however cannot determine what the quality of these values is. Of course, if you land the plane manually, then this does not influence anything and thus does not matter.

BTW, do you also get a max_distance of 25m when you run the "ll40ls test" command from the shell?

The 25m max distance value was set some time ago and makes sense, because the sensor actually gets quite unreliable above 25m (although it can of course measure higher distances).

authors: IeiuniumLux philipoe priseborough


text:
🛑 Free CDN is down

In b8626d1, Free CDN (https://cdn.onedns.ch) was down:

HTTP code: 530
Response time: 108 ms

Resolved: Free CDN is back up in d85b217 after 2 days, 11 hours, 16 minutes.

repo: Pablo-Wynistorf/uptime


text:
Version 0.3.4 - key doesn't refresh table

Only on version 0.3.4: When using key in AgGrid the table doesn't refresh anymore, no matter if you try to set reload_data or update_mode.
The issue doesn't appear in version 0.3.3, I currently reverted the package version, but a fix of the problem is quite urgent.

I think when you generate an  aggrid table with a key,  it will create a memory space and won't be free. When you change your df, but do not change the key, aggrid table will return the table of last key in memory space. If you change the key, i think table will reload. I set the key as the hash value of df, so when the df change, aggrid will create a new table. But here is a big problem, i find the st aggrid will never free its memory space, even i use the gc.collect() and del the variable. That makes memory leak, i cannot solve it...

repo: PablocFonseca/streamlit-aggrid


text:
#397 Adding a note for sensitive values

Description
This pull request includes an update to the docs/configuration.md file. The change adds a new section on handling sensitive data in the Tapir configuration.
The most significant change is:

docs/configuration.md: Added a new section, "Note Regarding Sensitive Data", providing guidance on how to handle sensitive data like keys, passwords, connection strings, etc. The update recommends using a secret manager like AWS Secrets Manager or Azure Key Vault, and provides information on  using Opaque Kubernetes Secrets for users operating in a Kubernetes environment.

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Fixes #397

repo: PacoVK/tapir


text:
Convert number to hex

As far as I know, it's currently only possible to display a hexadecimal number as decimal by entering it with 0x or _16. It would be neat to have a function to convert a decimal number to hexadecimal.
Example:
>> hex(123456)
0x1e240

This was definitely needed! I ended up making a "base" command instead of having a function, since numbers aren't represented as a particular number base under the hood. Now you will be able to do eg. base 16 and get all results in hexadecimal (as well as decimal).

Thank you!


text:
Support FP16 calculation

Hi!
Does Deep Speech support calculations using FP16 ?
We are interested in this problem, because Nvidia v100 shows more TFLOPS with FP16 than FP32.
Thanks.

Because the V2 API in PaddlePaddle we use doesn't support FP16, so we don't have the plan yet

authors: VictorBebnev kuke

repo: PaddlePaddle/DeepSpeech


text:
demo_server问题

我用mac去跑demo_server. 我的demo_server是可以跑出来，运行效果如下：
Warming up ...
('Warm-up Test Case %d: %s', 0, u'/Users/Desktop/DeepSpeech/data/aishell/wav/test/S0913/BAC009S0913W0364.wav')
Response Time: 3.273213, Transcript: 邀请专家学者等三十馀人组成志愿者培训导师
('Warm-up Test Case %d: %s', 1, u'/Users/Desktop/DeepSpeech/data/aishell/wav/test/S0912/BAC009S0912W0384.wav')
Response Time: 1.695054, Transcript: 冰雪爱好者不得不选择出国
('Warm-up Test Case %d: %s', 2, u'/Users/Desktop/DeepSpeech/data/aishell/wav/test/S0902/BAC009S0902W0467.wav')
Response Time: 1.467976, Transcript: 黄色渣土车一头撞进了路边的攻防
ASR Server Started.
但是我的demo_client.py不知道有没有运行成功，我输入python -u deploy/demo_client.py --host_ip 'localhost' --host_port 8086， 也没有报错。只是没有任何反应，我按空格键，client端就出现空格，并没有录音，按“esc"键也不会退出。同时server端没有任何输出。我是在同一台机子上跑的，不知道有什么问题，请教一下，谢谢！

已经解决！