silo.py tests (36-39) error reading wave_1file.visit on Windows

Describe the bug
These tests are in the skip list for Windows because the file cannot be read.
The .visit file contains entries of the form wave_1file.silo:cycle_0000
The error message: The file "wave_1file.silo:cycle_0000" does not exist.
There seems to be a parsing bug somewhere that is causing it to barf on the : in the middle of the file name.
Not sure if it is during parsing of the .visit file, or when the Silo reader is passed that file name
Expected behavior
If this is a valid specification that works on other platforms, it should work on Windows, too.
Desktop

OS and version: Windows
VisIt Version: develop

I would be fine skipping on windows. That said, to explain the test. This is an odd-ball use of silo where all the time steps are in one silo file, just in different dirs in the file.
I dunno what people think of supporting this use case. There is nothing about Silo that prevents it. And, I did recall a user who generated a ton of timesteps in a >multigigabyte silo file that couldn't then view  their results in VisIt without this feature. It was long, long ago though.

Actually, the problem is that the wave_1file.silo:cycle_xxx files are symlinks to wave_1file.silo and symlinks aren't working. They may work on some Windows systems, but not my testing machines, they are disabled by policy.
So, they should be skipped on Windows. I can add an if-test to the .py file with comments as to why it is skipped on Windows, will that be sufficient so it can be removed from skip list?


Makefile: work-around to install ravenpy with binaries

The syntax in environment.yml and requirements.txt do not allow specifying pip options for ravenpy and old raven_dev, ostrich_dev make target not working anymore.
To fix make test-notebooks errors;
docs/source/notebooks/Climatological_ESP_forecasting::ipynb::Cell 1 Traceback (most recent call last):                                                                                File "/home/lvu/.conda/envs/raven/lib/python3.7/site-packages/pywps/app/Process.py", line 249, in _run_process
    self.handler(wps_request, wps_response)  # the user must update the wps_response.                                                                                File "/zstore/repos/raven/raven/processes/wps_climatology_esp.py", line 93, in _handler
    model_name, forecast_date, forecast_duration, workdir=self.workdir, **kwds
  File "/home/lvu/.conda/envs/raven/lib/python3.7/site-packages/ravenpy/utilities/forecasting.py", line 103, in perform_climatology_esp
    m = get_model(model_name)(workdir=workdir)
  File "/home/lvu/.conda/envs/raven/lib/python3.7/site-packages/ravenpy/models/emulators.py", line 49, in __init__
    super().__init__(*args, **kwds)
  File "/home/lvu/.conda/envs/raven/lib/python3.7/site-packages/ravenpy/models/base.py", line 105, in __init__
    "Could not find raven binary in PATH, and RAVENPY_RAVEN_BINARY_PATH env variable is not set"
RuntimeError: Could not find raven binary in PATH, and RAVENPY_RAVEN_BINARY_PATH env variable is not set

Oh scratch that, with my fix, the raven binaries still not found in the notebooks !  I guess the fix is not 100% complete.  I'll have to add something more ...

Oh scratch that, with my fix, the raven binaries still not found in the notebooks !  I guess the fix is not 100% complete.  I'll have to add something more ...

Alright, got it this time.  Had to fully uninstall and reinstall ravenpy with the proper pip options.
So this brings to the next observation: the environment.yml and requirements.txt are essentially broken/incomplete since they install ravenpy without the binaries.
Looks like we have yet another reason to work on https://github.com/CSHS-CWRA/RavenPy/issues/42.

Alright, got it this time.  Had to fully uninstall and reinstall ravenpy with the proper pip options.
So this brings to the next observation: the environment.yml and requirements.txt are essentially broken/incomplete since they install ravenpy without the binaries.
Looks like we have yet another reason to work on https://github.com/CSHS-CWRA/RavenPy/issues/42.


Strategy for adding more model parameters within the blocked Gibbs Sampling framework by adding more blocks

I had an idea while watching a video on Gibbs sampling (the bit beginning at roughly 1h09m):  Maybe we can adapt the Gibbs sampler to deal with correlated parameters after all.  I'm not sure how to implement it, but the main procedure would be something like this:

Update ~6 Nuissance Parameters, holding everything else fixed
Update ~6 traditional stellar parameters (à-la Czekala et al. 2015)
new Update whatever new stellar model parameters you've added (e.g. veiling, starspots, binary, whatever)

My guess is that this three-level blocked Gibbs sampler would outperform a two-level Gibbs with the new stellar parameters included in block 2.
For example, I witnessed poor convergence when I attempted to fit a mixture model with ~8 stellar parameters (3 of which were strongly correlated) in block 2, as discussed in detail in Issue #35.  That tension led me to a major departure from the Gibbs sampler, in which I run emcee to sample all 14 stellar+nuisance parameters simultaneously, but with the major limitation that I had to chunk by spectral order thereby deriving multiple independent sets of stellar posteriors for ~50+ spectral orders.  The extension to the Gibbs framework described here, if it can be implemented, would return to the much better situation of having a single posterior that is consistent with all the data.
This seems obvious in hindsight, so it must be a good idea, right?

It should be noted that the three-block procedure would take ~1.5x longer than the existing 2-block procedure, but the Metropolis-Hasting convergence time would be superior in the 3-block case.
It should also be noted that the three-block procedure would be roughly N_walkers/3 x faster than the emcee modification (described above), for the same number of spectral orders equal to the number of CPUs.  In my case of n_orders ~ n_walkers ~ n_cpus = 40, this would naively be a 10x speedup, but there's still the non-negligible albeit ameliorated problem of tuning the steps for the Metropolis Hastings, so the emcee modification is not quite so terrible, especially in human-attention time; it's main demerit is   yielding too many inferences that have to be combined with heuristics and the sensitivity to order-level systematics.

I'm all for new implementations of the sampling procedure, especially if they can be done in a modular fashion. I'm a little unclear on how breaking the additional parameters (i.e., spot coverage fraction, T_eff_2, etc...) into a separate Gibbs step will help with the correlation. Since these parameters will still be correlated with the parameters in step #2, wouldn't it be faster to tune the M-H jump in step 2 to the correlations of the space? As you point out, in general this is a pain to do, since it requires first burning in some runs using a guess at the correlation, and then restarting the chain with a (noisy) estimate of the correlation made from the previous samples. Are you thinking that the third Gibbs step would ameliorate this issue?

Are you thinking that the third Gibbs step would ameliorate this issue?

I assumed so based on watching the Iain Murray video segment in which he introduces Gibbs sampling as a way to ameliorate correlated samples.  It's also mentioned in this Hogg Blog post:
http://hoggresearch.blogspot.com/2012/12/emcee-vs-gibbs.html
You're right that tuning the MH sampler should work, and it does for sampling normal singleton stars.  The problem only arises in practice for starspot models where I observed acceptance fractions <<1%.  I suppose iteration on the tuning parameters would eventually work, but again, in practice this was a pain and involved lots of human intervention.  One alternative would be to make analytic affine transformation of variables-- we know the logOmegas will correlate in a relatively predictable way, for example.  My hope was that tweaking the Gibbs sampler would avoid this step so that adding extensions to the model would be relatively effortless for the user.


added update and download button to imageDetails page

I added a update and download button to the imageDetails page. Following this issue.

Codecov Report

Merging #120 (1da2e05) into master (c21dd71) will decrease coverage by 0.64%.
The diff coverage is 0.00%.

:exclamation: Current head 1da2e05 differs from pull request most recent head 2ebedc6. Consider uploading reports for the commit 2ebedc6 to get more accurate results

@@            Coverage Diff             @@
##           master     #120      +/-   ##
==========================================
- Coverage   27.76%   27.12%   -0.65%
==========================================
  Files          70       70
  Lines        1228     1257      +29
  Branches      320      325       +5
==========================================
  Hits          341      341
- Misses        819      848      +29
  Partials       68       68

Impacted Files
Coverage Δ

src/Routes/ImageManagerDetail/DetailsHeader.js
0.00% <0.00%> (ø)

src/Routes/ImageManagerDetail/ImageDetail.js
0.00% <0.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 c21dd71...2ebedc6. Read the comment docs.


Update supported BGP knobs in VRF

Change Summary

Adds timers bgp, send-community, next-hop-self, and  description.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes)
[ ] Documentation content changes
[ ] Other (please describe):

Related Issue(s)

Fixes #489
Component(s) name
Proposed changes

eos_cli_config_gen
How to test

Molecule + HW
Checklist:

[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed (pre-commit, make linting and make sanity-lint).
[x] I have updated molecule CI testing accordingly

Changes pushed, molecule successful, and ready for review.


KeyError: "BasicVSR: 'BasicVSRPlusPlus is not in the model registry'"

Hi,
I am training BasicVSR++ from scratch on HPC cluster with following environment info:
`> sys.platform: linux
Python: 3.8.12 (default, Oct 12 2021, 13:49:34) [GCC 7.5.0]
CUDA available: True
GPU 0: Tesla T4
CUDA_HOME: /usr/local/cuda
NVCC: Build cuda_11.0_bu.TC445_37.28845127_0
GCC: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16)
PyTorch: 1.9.0
PyTorch compiling details: PyTorch built with:

GCC 7.3
C++ Version: 201402
Intel(R) oneAPI Math Kernel Library Version 2021.4-Product Build 20210904 for Intel(R) 64 architecture applications
Intel(R) MKL-DNN v2.1.2 (Git Hash 98be7e8afa711dc9b66c8ff3504129cb82013cdb)
OpenMP 201511 (a.k.a. OpenMP 4.5)
NNPACK is enabled
CPU capability usage: AVX2
CUDA Runtime 10.2
NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_37,code=compute_37
CuDNN 7.6.5
Magma 2.5.2
Build settings: BLAS_INFO=mkl, BUILD_TYPE=Release, CUDA_VERSION=10.2, CUDNN_VERSION=7.6.5, CXX_COMPILER=/opt/rh/devtoolset-7/root/usr/bin/c++, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_KINETO -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, LAPACK_INFO=mkl, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, TORCH_VERSION=1.9.0, USE_CUDA=ON, USE_CUDNN=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON,

TorchVision: 0.10.0
OpenCV: 4.5.4
MMCV: 1.4.6
MMCV Compiler: GCC 7.3
MMCV CUDA Compiler: 10.2
MMEditing: 0.13.0+793d026
`
After stopping the training due to time limit in cluster, I resume the training using config file basicvsr_plusplus_c64n7_8x1_600k_reds4.py :
--resume-from .../results/BasicVSR_plus_plus/train/iter_565000.pth
However I got the following error:
KeyError: "BasicVSR: 'BasicVSRPlusPlus is not in the model registry'"
This is while I resumed the training two times ago and it worked without problem.
The complete error message:
`Traceback (most recent call last):
File "/kuacc/users/nrahimi19/miniconda3/envs/mmlab/lib/python3.8/site-packages/mmcv/utils/registry.py", line 52, in build_from_cfg
return obj_cls(**args)
File "/scratch/users/nrahimi19/mmediting/mmedit/models/restorers/basicvsr.py", line 40, in init
super().init(generator, pixel_loss, train_cfg, test_cfg,
File "/scratch/users/nrahimi19/mmediting/mmedit/models/restorers/basic_restorer.py", line 48, in init
self.generator = build_backbone(generator)
File "/scratch/users/nrahimi19/mmediting/mmedit/models/builder.py", line 31, in build_backbone
return build(cfg, BACKBONES)
File "/scratch/users/nrahimi19/mmediting/mmedit/models/builder.py", line 22, in build
return build_from_cfg(cfg, registry, default_args)
File "/kuacc/users/nrahimi19/miniconda3/envs/mmlab/lib/python3.8/site-packages/mmcv/utils/registry.py", line 44, in build_from_cfg
raise KeyError(
KeyError: 'BasicVSRPlusPlus is not in the model registry'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/scratch/users/nrahimi19/mmediting/tools/train.py", line 150, in
main()
File "/scratch/users/nrahimi19/mmediting/tools/train.py", line 113, in main
model = build_model(
File "/scratch/users/nrahimi19/mmediting/mmedit/models/builder.py", line 60, in build_model
return build(cfg, MODELS, dict(train_cfg=train_cfg, test_cfg=test_cfg))
File "/scratch/users/nrahimi19/mmediting/mmedit/models/builder.py", line 22, in build
return build_from_cfg(cfg, registry, default_args)
File "/kuacc/users/nrahimi19/miniconda3/envs/mmlab/lib/python3.8/site-packages/mmcv/utils/registry.py", line 55, in build_from_cfg
raise type(e)(f'{obj_cls.name}: {e}')
KeyError: "BasicVSR: 'BasicVSRPlusPlus is not in the model registry'"
`
Could you please help?

BasicVSR++ should not be in the model registry. It should be in the backbone registry.

Thanks for your response  @ckkelvinchan
How can I fix it? Using config file?
I did change nothing in config file but --resume-from .../results/BasicVSR_plus_plus/train/iter_565000.pth. What may cause this error?

This is a bit strange. How about trying to use the resume_from in the configuration file?

Dear @ckkelvinchan
I found out that I have removed @BACKBONES.register_module()  in basicvsr_pp.py file by mistake,
I fix it and it works without problem.
Thank you


 not firing updates or observers on select

In working with iron-list I discovered what I believe to be an issue with array-selector.
When the value of selected is changed (a user selects/deselects items) the <property>-changed event as well as any observers associated with the property are not firing.
The example provided here is using iron-list however if you put an observer on iron-list's selectedItems prop you will see the same behavior.
https://jsfiddle.net/jshcrowthe/L936q2mq/4/

In multi-select mode, selectedItems is going to be an Array, not an object. And if you want to listen for change events when items are added or removed from it, you'll need to register an observer like this:
  observers: [
    '_logChange(selected.*)'
  ],
  _logChange: function(changeRecord) {
     ...
  }

You'll need to change the observer and check the change record's path property to  filter out the changes you're interested in.

@arthurevans Thanks for getting back to me so quick!
So if I am understanding correctly because it's an Array in a property declared type Object there aren't any notifications that fire when any of the Array helpers are used then?

@jshcrowthe No, the declaration of Object doesn't really have any effect here. It's only used when you set a property from markup with a string literal.
You're not getting notifications on a simple property observer because the value of selected isn't changing—it's still the same old array, it's just getting new items added and removed. That's why you need an array observer or deep property observer.

Wow, in tinkering with this I realized I totally misunderstood what the array mutation methods are doing, I was under the impression that they also notified those listening on an array that the array had changed.
Is this intentional behavior? Or is this something that could be changed? It seems like the array having an item added to it changes the array.


feat: drop Python 3.10 and add Python 3.12

Summary of Changes

Remove support for Python 3.10
Add support for Python 3.12

:tada: This PR is included in version 0.16.0 :tada:
The release is available on:

v0.16.0
GitHub release

Your semantic-release bot :package::rocket:


Add extension to be executed only once

Basic trainer.Extension class is implemented for iterated extensions.
However, sometimes we need the extensions to be executed only once.
(There is only one such official extension dump_graph.)
This PR provide the base class for such extensions.

Sorry for the late response. I thought this feature should be covered by a trigger instead of an Extension subclass. What do you think about introducing such a trigger, say TriggerOnce?

Thanks to your recommendation. I re-implemented this feature as trigger instead of extension, and use name OnceTrigger for consistency with other triggers.

Sorry for late response.
I updated training.rst.

Looks good. Could you add simple tests for this trigger? (sorry for mentioning it late)[


Update language selection forum links

What is the context of this PR?
Fixes: #1143
How to review
Check links are correct

 Issue #1143: Wrong link to Design Forum in 'Change language' pattern

Can we just change title 'Change language' to use lowercase L?


Refactor server

Changes

Refactored directory structure
Removed gorilla dependency since all of this can be easily done with stdlib (also I could not quickly figure out why the gorilla router would not correctly set the error header in w in certain cases - stdlib works fine
More idiomatic Go style, also using functional options to configure the server
structured logging using zap
Default server port is 8080 to comply with Buildpacks/Knative
Configurable via environment variables using envconfig
Counter is incremented on every produced/successfully sent event (/produce handler)
Retries in client.Send()

Closes: #1
Feel free to modify the code/const values and defaults (in options.go). With functional options, I could remove getEnv logic and added the popular envconfig to configure the server via environment variables and inject the values during server.New(ctx, server.WithSink(...), server.With...), etc.
go test -v -race -count 1 ./... -json -cover | tparse -all

+--------+---------+---------------------------------------------------------------------+------------------------+
| STATUS | ELAPSED |                                TEST                                 |        PACKAGE         |
+--------+---------+---------------------------------------------------------------------+------------------------+
| PASS   |    0.00 | TestOptions                                                         | fmtok8s-go-cloudevents |
| PASS   |    0.00 | TestOptions/empty_sink                                              | fmtok8s-go-cloudevents |
| PASS   |    0.00 | TestOptions/empty_address                                           | fmtok8s-go-cloudevents |
| PASS   |    0.00 | TestOptions/ce_protocol_nil                                         | fmtok8s-go-cloudevents |
| PASS   |    0.00 | TestOptions/ce_client_nil                                           | fmtok8s-go-cloudevents |
| PASS   |    0.00 | TestServer_Run                                                      | fmtok8s-go-cloudevents |
| PASS   |    0.00 | TestServer_Run/stops_server_on_context_cancellation                 | fmtok8s-go-cloudevents |
| PASS   |    0.00 | TestServer_sendCloudEventHandler                                    | fmtok8s-go-cloudevents |
| PASS   |    0.00 | TestServer_sendCloudEventHandler/fails_when_http_method_is_not_POST | fmtok8s-go-cloudevents |
| PASS   |    0.00 | TestServer_sendCloudEventHandler/sends_cloudevent_on_produce        | fmtok8s-go-cloudevents |
| PASS   |    0.00 | TestServer_consumeCloudEventHandler                                 | fmtok8s-go-cloudevents |
| PASS   |    0.00 | TestServer_consumeCloudEventHandler/consumes_cloudevent             | fmtok8s-go-cloudevents |
+--------+---------+---------------------------------------------------------------------+------------------------+

+--------+---------+-------------------------------------------+-------+------+------+------+
| STATUS | ELAPSED |                  PACKAGE                  | COVER | PASS | FAIL | SKIP |
+--------+---------+-------------------------------------------+-------+------+------+------+
| PASS   | 0.45s   | github.com/salaboy/fmtok8s-go-cloudevents | 82.5% |   12 |    0 |    0 |
+--------+---------+-------------------------------------------+-------+------+------+------+

@embano1 sorry that this is taking time.. COVID this week and I wanted to make notes of all the changes so I can document a bit for a talk that I am preparing

Easy my friend, let me know if things are unclear or should be changed. Code and style is always something very personal :)


Update tutorials running locally page

The current Running locally page under Tutorials is missing an important command without which the NPM project won't be initialized and none of the dependencies can be installed.
Have added the npm init -y command before installing dependencies. (this was present in PR #888 earlier but I think after the last change before merging it got removed by mistake).
Before:

After

Tag #891

@proudofsimin I have changed "initialise" to "initialize"

@Rohitesh-Kumar-Jain I think this PR can be added to #1056


Default backup TTL of 24hrs is too short

Maybe this is an edge case but I went to restore some backups I made from yesterday and was surprised to discover they were gone.  I suppose the expected use case is to start in restore-only mode so this wouldn't happen, but it does seem like a longer default TTL would make more sense, maybe 72h? A week?

Thanks for the feedback, @blakebarnett. That's probably a good change to make to the default going forward. Care to submit a PR? :) No worries if not, we'll keep the issue open.

How about 30 days?


Plotly: Add Panel-based support for linked streams and dynamic updates

Reopened #3866 against master
Overview
This PR supersedes https://github.com/pyviz/holoviews/pull/3316, building linked stream support on top of the HoloViews Panel integration started in the base branch (philippjrf/widgetsectomy).  Supported linked streams are:

RangeXY
RangeX
RangeY
BoundsXY
BoundsX
BoundsY
Selection1d

It also adds support for updating DynamicMaps using streams from Python.
@philippjfr @jlstevens @jbednar
Linked Streams Architecture
The core implementation of linked streams is in ff0eb73.  Here's an overview
Every Plotly ElementPlot now has a trace_uid property. This trace_uid is used as the uid property of the Plotly trace that will be associated with any linked stream attached to this plot's Element.
This plot element is an input to a new set of PlotlyCallback classes.  Each callback class is responsible for tracking all active instances if its own class type using a WeakValueDictionary from trace_uid to callback instance. (To reduce boilerplate the instance tracking logic is in the MetaPlotlyCallback metaclass).
Additionally, each callback class is responsible for dispatching callback events to the streams of all relevant callback instances.  This dispatching is done in the update_streams_from_property_update class method of each callback class.
When the plotly backend is activated, a backend switch hook is used to register a custom plotly pane construction function with the Panel HoloViews class.  This function is responsible for constructing the Plotly pane instance for the HoloViews pane. In addition, it also installs callbacks to call the update_streams_from_property_update methods when the appropriate callback parameter is updated.
Dynamic Update Architecture
The core implementation of dynamic update support is in 6352793. Here's an overview.
The id property of PlotlyPlot instances is now set to a random UID.  This id is added as a top-level _id key in the plotly figure dictionary produced by the plot class. (this property is removed before the user would get it by calling hv.render, see 845f423baff59538679ff7f2918dfa9a939dd7d9).
The custom Plotly pane constructor function described above creates a mapping between the _id property in the figure dictionary and the associated plotly pane that is constructed.  This mapping is stored as a class level WeakValueDictionary in the PlotlyRenderer class.
The PlotlyRenderer class has a new trigger_plot_pane class method that inputs a plot id and a new figure dictionary, and it is responsible for updating the appropriate plotly pane to the updated value.  This method is called by the various update_frame methods across the PlotlyPlot class hierarchy.
Other changes
The remaining commits are pretty small and self explanatory I think.  Let me know if you have any questions about them!
Examples
The examples from https://github.com/pyviz/holoviews/pull/3316 still work as-is.

@jonmmease I rebased this PR because I forgot to merge it against the PR before merging. It was very painful and I may have messed this up, so could I ask you to test it?

Wow, thanks for taking on this rebase @philippjfr.  Yes, I'll review and test soon!


Don't have IE9 support for closing of selected node

Is it possible alternative implantation of closing of selected node for IE9. I have tested in IE 9. I am unable to removed selected not in IE9.

Kindly paste the below code above node.remove() in the js file, then it should work fine
if (!('remove' in Element.prototype)) {
Element.prototype.remove = function() {
if (this.parentNode) {
this.parentNode.removeChild(this);
}
};
}


Create a seedable random number generator

This adds jsPsych.randomization.setSeed(), which uses the seedrandom package to create a seedable random number generator.
In order to make experiments reproducible without relying on replacing all calls to Math.random() with calls to a jsPsych-specific PRNG, setSeed() takes advantage of seedrandom's ability to replace Math.random() with a seedable PRNG. Thus, calling setSeed changes the global behavior of Math.random(). This is probably desireable in 99.9% of cases where someone would want to use this feature.

@becky-gilbert @bjoluc
Would love your input on the design decision here to override Math.random(). I considered creating a separate PRNG scoped to the instance of jsPsych, but that would require replacing all Math.random() calls in an experiment with calls to that PRNG. The scenario that convinced me that this was not a good idea was that if someone is using a non-jsPsych library as a component of a jsPsych experiment, then they would need to edit that library to make it reproducible with this feature. Changing the global behavior of Math.random() seems like it has far fewer downsides.

@bjoluc it looks like there are build errors here related to Turbo. I'm guessing I merged something wrong, but can you take a look?

This pointed me towards a Turbo build dependency problem on main that I just fixed (test-utils didn't depend on jspsych via its dev dependencies). Then 0509199 was required here since Turbo doesn't seem to check for circular dependencies, but prefers to hang instead :sweat_smile:  The remaining test failure is just the number vs string thing :tada:


Enable env variable to configure Bonsai poll time and reduce default

Tested on low-latency proof workflows, and cuts those e2e snark times using this prove API by ~5s (as expected).
As for what the default is, just going with the upper limit of what @mothran suggested Bonsai can handle.
Keeping the TODO and #1759 open given this is still a very naive solution and could be improved. Before we are able to consider adding a WS API for this, we could do some of the following:

[ ] Add a backoff function to the stark polling by default, to minimize server requests for long proofs

Possibly also having each configurable

[ ] Separate the Snark and Stark polling intervals, have them both be configurable
[ ] Add an initial delay for Starks or Snarks for the minimum duration we estimate

But I decided to keep it as simple as possible because it is unclear the direction of this in the long term.

Is this able to land before next release? Would be very helpful. Unclear if comment is viewed as blocking, happy to change logic if so.

This didn't make it into 1.1.0, but we can do 1.1.1


Points/values not visible in star view; low [m] values threshold ?

i've come a long way since starting the use of Bonsai, and as I'm working towards using real quantum values in a bonsai graph I found that some values are not visible in star-view but are visible in points-view as blue dots. Is there a range/reason when those values are not displayed ? Is this range known, so I can adapt values for those settings and get all point/values displayed in star-view. The image below is one with star view the bottom image is point view ( P key )  [ graph is in a mobius form ]

Looking at your bottom figure it looks like the particles that are blue there do not show up in the rendered part. Bonsai classifies particles primarily by it's ID and blue is the colour for dark-matter particles.
If instead these are all star particles, then maybe indeed the mass of those can come in to play. The color for star particles is determined in this file.
So I would first check what IDs you give to the particles.

ID is 2, stars. So far this has always been the case as the particles are for visualisation.
looks like mass is too high for that part. Thank you for the list, i can adjust for this now


onAuthLogout not fired when calling keycloak.logout()

I implemented the onEvent handler like this:
const keycloak = new Keycloak();

const keycloakConfig = {
  onLoad: 'check-sso'
};

const onTokens = tokens => {
  window.localStorage.setItem('authToken', tokens.token);
};

const onEvent = (event, error) => {
  console.log('onKeycloakEvent', event, error);
  if (typeof error !== undefined) {
    switch (event) {
      case 'onAuthSuccess':
        window.localStorage.setItem('authenticated', keycloak.authenticated);
        break;
      case 'onAuthLogout':
        window.localStorage.setItem('authenticated', false);
        window.localStorage.setItem('authToken', null);
        break;
      case 'onTokenExpired':
        window.localStorage.setItem('authenticated', false);
        window.localStorage.setItem('authToken', null);
        break;
      default:
        break;
    }
  }
};

ReactDOM.render(
  <KeycloakProvider
    keycloak={keycloak}
    initConfig={keycloakConfig}
    onEvent={onEvent}
    onTokens={onTokens}
  >
    <BrowserRouter>
      <App />
    </BrowserRouter>
  </KeycloakProvider>,
  document.getElementById('root')
);

The onAuthSuccess is working fine, but when I call keycloak.logout() the onAuthLogout event is not fired. Did I get something wrong here?

Hi @Bowfish ,
That's odd, using the following code in the demo of react-keycloak, I see the event firing correctly, when calling logout;
import { AppRouter } from './routes';

const keycloak = new Keycloak();

class PersistedApp extends React.Component {
  constructor(props) {
    super(props);

    this.tokens = JSON.parse(localStorage.getItem('kcTokens') || '{}');
  }

  onKeycloakEvent = (event, error) => {
    console.log('onKeycloakEvent', event, error);
  }

  onKeycloakTokens = tokens => {
    console.log({ tokens });
    localStorage.setItem('kcTokens', JSON.stringify(tokens));
  }

  render() {
    return (
      <KeycloakProvider
        keycloak={keycloak}
        initConfig={{
          onLoad: 'check-sso',
          ...this.tokens,
        }}
        onEvent={this.onKeycloakEvent}
        onTokens={this.onKeycloakTokens}
      >
        <AppRouter />
      </KeycloakProvider>
    );
  }
}

This PersistedApp component is used instead of the App one in the demo code you can find under src/demo of this repo.
Which version of Keycloak-js and react-keycloak are you using?
The demo is using
"keycloak-js": "^6.0.1",
"react-keycloak": "6.0.4",

That's really odd. I tried your PersistedApp and I can see the logout event firing.
I'm also using:
"keycloak-js": "^6.0.1",
"react-keycloak": "6.0.4"

The only difference in my app is that I use keycloak.login({ redirectUri: 'http://localhost:3000/' }). Might that be the reason?

I don't think that should be an issue since we're talking about onAuthLogout event.
How are you calling keycloak.logout method?
Also I'd recommend you to avoid saving the user token and authenticated inside localStorage since you can always retrieve that data from a keycloak instance (which is safer and always guaranteed to be in-sync with the actual Keycloak user-session).

I'm calling it like this:
const onClickUserLogout = event => {
    keycloak.logout({ redirectUri: 'http://localhost:3000/logout' });
};

The function is called by a button event.
Thanks for the hint. You are right. that is much safer.

I quick test you can make is try to connect react-keycloak demo to you Keycloak instance and check if it works as you expect, then have a look at src/demo/pages/Home.js to have a look at how I would implement a logout on button click.
To try the demo:

download the repo code,
run yarn,
place your keycloak.json in the public folder
run yarn start
try login and logout

I don't think it is an issue, the logout event is working for me.

panz3r, suppose if I logout the user session in  keycloak Admin Console. (Users -> Session -> Logout ) , will the logout event fired? Is there any solution to listen such kind of logout events?

panz3r, suppose if I logout the user session in keycloak Admin Console. (Users -> Session -> Logout ) , will it fire the logout event? If not Is there any solution to listen such kind of logout events?

Hi @charan1922 ,
I made a couple of tests about your request, and it turned out that onAuthLogout is actually called even in the case the user clicks Logout from Keycloak Console.
If the web-app integrating react-keycloak is opened in another tab the event is fired immediately, otherwise the event is fired right before the onReady event the next time the web-app is opened.


[Bug]:  pig game doesnot have instructions before

Give a brief about the bug ✍
Description:
every player requires instructions about how to play without that they dont show much intrest so
many of the games doesnt have instructions before one of them is pig game.
What is the expected behavior? 🤔
Description:
alerting the player how to play before game starts!
Provide step by step information reproduce the bug 📄
Description: before starting the game one alert should come with all proper instructions about how to play.
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

assign this task to me

Hey @jahnaviyallamelli !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

can you assign this task to me i want to work on it

Hey can you assign this task to me I want to work on this.

I would to work on this. can you please assign this to me...???

I would to work on this. can you please assign this to me...???

/assign

/assign

Hey @jahnaviyallamelli ! , This issue is already assigned to @shaklan2001. 💗
You can work on other issues 🚀
If there is anything wrong you can contact us on Discord🕹👀

Hey @jahnaviyallamelli ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


MP-18.01 Cold start callback framework

Ref : https://github.com/K2InformaticsGmbH/mpro/issues/208
Cold start callback hook framework

On start the provided / installed cold start callback function (if configured and enabled through application environment parameter cold_start : boolean) will be called if "cold start" (single and first node in the cluster) is detected
default cold start callback function will also be inserted to ddConfig for future customization

Using DDErl cold start callback hook framework in host applications
Applications (using DDErl as dependency) will be able to use this feature through a single macro COLDSTART_CB(Fun) defined in dderl.hrl as:
?COLDSTART_CB(Fun) % Fun is a binary function string to be compiled by `imem_compiler`
?COLDSTART_CB(Fun) % Fun is a erlang `fun` term

In both cases (fun or binary) a valid hook function is expected to be of arity 0
A typical usage example would be:
-module(some_application).
-behaviour(application).

%% OTP Application API
-export([start/2, stop/1]).

%%-----------------------------------------------------------------------------
%% Application Interface
%%-----------------------------------------------------------------------------
start(_Type, _Args) ->
    ...
    ?COLDSTART_CB(<<"fun() -> write_your_hook end">>),
    % OR
    ?COLDSTART_CB(fun some_application_mod:coldstart_hook/0),
    ...
    some_application_sup:start_link().

Optional environment parameters for host application (DDErl as dependency)

cold_start : boolean

If optional application parameter is not / incorrectly defined and COLDSTART_CB(Fun) macro is PRESENT in application start/2 OTP callback, application will continue to load with suitable error / warning
If COLDSTART_CB macro is NOT PRESENT in application start/2 OTP callback this feature will be disable and application will continue to load normally

@shamis removed application parameter cold_start_fun


Richardson number profile output jumps around and is not smooth

The Richardson number profile in the strong wind case and free convection case doesn't seem to be correct,
https://engaging-web.mit.edu/~alir/lesbrary/6DaySuite/three_layer_constant_fluxes_linear_hr144_Qu0.0e+00_Qb5.0e-08_f1.0e-04_Nh256_Nz128_free_convection/instantaneous_statistics.mp4
https://engaging-web.mit.edu/~alir/lesbrary/6DaySuite/three_layer_constant_fluxes_linear_hr144_Qu7.0e-04_Qb0.0e+00_f1.0e-04_Nh256_Nz128_strong_wind/instantaneous_statistics.mp4
The profile looks very jagged in regions were it should be smooth, and jumps around sometimes.

For free convection the Richardson number isn't well defined (if computed from horizontal averages) because the mean shear is close to zero, right?

yeah, since the mean shear is close to zero, shouldn't Ri be a huge number in the region? It looks like at certain grid points it drops to below zero. That can be seen in the strong wind case as well.

True, I guess I would expect it to be uniformly large. Certainly dz(B) is never < 0, so Ri should be strictly positive. Can you screen shot a problematic frame in the movie and paste it here?

Here you go!

Right so while Ri attains very large values as expected, it also appears to attain low values below 0 which is unexpected. Where is Ri calculated?

https://github.com/CliMA/LESbrary.jl/blob/371ce34cbc4352c58ef40358e993b3797acc9d33/examples/three_layer_constant_fluxes.jl#L407
It's here! I have been using this script to run simulations.

and where is richardson_number_ccf! defined?
It looks like this might be the horizontal average of the local (3D) Richardson number, rather than the ratio between dz(B) and (dz(U)^2 + dz(V)^2), where the capitalized variables are horizontally-averaged. In that case, it is possible that Ri is less than zero because locally Ri can take on values close to - infinity?

So just to clarify the discussion, I'll mention that there are many definitions of the "Richardson number", and the physical interpretation of this quantity depends on how it is computed.
Most people define a "gradient" Richardson number as
Ri = dz(b) / (dz(u)^2 + dz(v)^2)
There is also a "bulk" Richardson number that can be interpreted as a ratio between potential energy and kinetic energy.
The first thing to mention is that the gradient Richardson number is fundamental to the instability of stratified shear flows. Instabilities often occur when Ri < 1/4. Note that the exact stability criterion depends on the entire flow profile and Ri < 1/4 is strictly only informative for linear shear and stratification. This is a subject of vigorous research in fluid dynamics.
The relative simplicity and predictive power of Ri < 1/4 means that it is often used as a "proxy for mixing" in stratified turbulence studies. Thus in DNS and LES it is common to measure the local Richardson number and interpret turbulent regions / behavior in light of this diagnostic quantity. This is the sense in which the quantity is defined in Oceanostics, where it is defined in three-dimensions, locally, and with the option to include a background flow around which the dynamics might be posed.
In parameterization, we use a quantity that is superficially identical to the local gradient Richardson number. However, this quantity is different than the local gradient Richardson number because it is defined on coarse-grained fields. For "exact" flows the criterion Ri < 1/4 is paramount. For coarse-grained fields, the specific Ri value is just an indicator the true, underlying subgrid distribution of Ri. Another interpretation of the coarse-grained Ri is the relative role of potential energy dissipation and kinetic energy dissipation in a turbulent flow.
Both the local and coarse-grained Ri are useful quantities. I'm not sure what we want to compute here. However, it is definitely the case that the horizontal average of the local Ri may not be very useful. The issue is that we lose information by horizontal averaging; and it is specifically the local value of Ri in that case which is useful.
Probably what we would like to compute is just dz(B) / (dz(U)^2 + dz(V)^2), where U, V, B are horizontal averages. There's no need to launch a kernel to compute these. We don't have a great way of expressing this computation in the current abstract operations framework. Perhaps this is something to work on.

Thanks for the explanation! I agree that Ri = dz(B) / (dz(U)^2 + dz(V)^2 seems to make the most sense in our case (boundary layer parameterizations).
Will reply to your last paragraph in PR #113.


add ts enum to core-type

Enums are semantically different in each type system / language, with different unique constraints. I'd recommend not using them for data structures that are shared across languages/protocols, and (if at all) only internally in unexposed details.
See https://github.com/grantila/typeconv/issues/8


GraphQL Queries stopped working all of a sudden

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
10.3.1
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
Nothin was done! GraphQL stop to work around 17h UTC
Amplify Categories
api
Amplify Commands
Not applicable
Describe the bug
GraphQL  stop to get the query... nothing was done...
They stop around 17UTC 21-Oct
I try manually test get the query using the AWS AppSync Online interface.
a this is when get weird!
I do my fetch using sortDirection: ASC (Was working fine!) now stop!

I'm receiving 0 item!
Now look what happen when i change to sortDirection: DESC

I get my list!
I really my list in ASC !
Expected behavior
I expect to have my in ASC  as well ... was working before

Reproduction steps

Go to GraphQL
query sortDirection: ASC nothing happen
query sortDirection: DESCnothing happen - i got the list

GraphQL schema(s)

# Put schemas below this line

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response

Hi @dubiella  👋 thanks for raising this issue.we are working on reproducing the issue, Could you please run below command and send us the report amplify diagnose --send-report

Hi @dubiella, Are you still experiencing this issue??

Hii @dubiella, I tried to reproduce the issue and found that the query functions are working correctly.
The schema used is :
type CatRequest @model @auth(rules: [{ allow: owner }]){
 id: ID!
 name: String!
 status: String
 type: String! @index(name: "CatRequestByDate", queryField: "CatRequestByDate", sortKeyFields: ["createdAt"])
 createdAt : String!
}

Using the above model, the queries will work correctly

The ASC sort:

The DESC sort:

Hi 👋 Closing this as we have not heard back from you. If you are still experiencing this issue and in need of assistance, please feel free to comment and provide us with any information previously requested by our team members so we can re-open this issue and be better able to assist you.
Thank you!

I am facing the exact same issue however, I don't know how to reproduce it, since it's code taken from official docs but suddenly all I am getting is Unhandled Promise Rejection
I did run the diagnose command:
Project Identifier: 9490f6e494d7caf7b17f4a9f98c9f6f5
report-1701850668667.zip


Bookmarklet script

I'm not certain if this applies universally across javascript engines (particularly older ones), but it's not required to use an anonymous function to load the mod. This applies to usage in both the bookmarklet and the browser console in the latest versions of Firefox and Chrome.
Instead of using:
javascript: (function () {
	Game.LoadMod('https://aktanusa.github.io/CookieMonster/CookieMonster.js');
}());

This is adequate:
javascript: Game.LoadMod('https://aktanusa.github.io/CookieMonster/CookieMonster.js');

The usual reason for the usage of anonymous functions is to avoid potential name collisions, but it doesn't seem necessary in this case since there's only a single function being called that is virtually guaranteed to be reserved to CookieClicker's Game.LoadMod() (assuming it's used on the correct page).
I would suggest recommending the trimmed down script by default, and leaving the other option as a backup for backwards compatibility issues. Unless of course there's a reason to use an anonymous function here that I'm not aware of.

I'll take a look.

Using an anonymous function isn't necessary, but is generally considered good practice. Since no one has commented on this for a while, and no one seems that concerned about it, I'm going to go ahead and close the issue.


chore: use code regions

They're editor fold regions.
I pulled this PR out of a series of other commits to untangle everything.


Component refactoring

It would be really nice to start splitting up the TaskList and TaskListItem from the TaskList.svelte file.
Having a more organised set of components will allow others to better aid development.

Yes, I think this should be done. 👍


variable typed as any improperly when object refer itself with type parameter

TypeScript Version:  3.1.3

Search Terms:
type, infer
Code
class FailInfer<T>{
    constructor(arg: ()=>T){}
}

const failed = new FailInfer<number>(()=>failed)

Expected behavior:
The ts server knows failed should be FailInfer<number> and the callback is not correctly typed.
Or it should tell the user it can't determine what the type is and force user to choose a proper one.
Actual behavior:
The failed is typed as any, so no error happend
Playground Link:
https://www.typescriptlang.org/play/#src=
class FailInfer<T>{
    constructor(arg%3A ()%3D>T)%7B%7D%0D%0A%7D%0D%0A%0D%0Aconst%20failed%20%3D%20new%20FailInfer%3Cnumber%3E(()%3D%3Efailed)
Related Issues:

However, the final result type is actully totally unrelated to i failed tself, the type parameter here is explicitly defined and unrelated to the type of failed

TS couldn't infer the type of failed because of reasons listed above and gave it an implicit type of any.
any is assignable to number.

Once a variable appears in its own initializer in a way that matters, it's always implicitly any. This is a known limitation of our current inference algorithm.


[Feat]: Profile Filtering based on their skills

What feature?
I have an idea ,
We can have filter feature to filter Profiles by their skills.
Add screenshots
Add screenshots
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@shyamtawli I would like to work on it.

There is already an issue for this and someone is working on it. So Closing the issue.


Multiple view projections

This project looks promising, great job!
What are the plans for handling projections from multiple angles and texture blending?
There are of course relevant use cases even from one perspective, but it does have limitations.

There are several promising directions like Paint3D. I plan to implement this and other methods in the plugin as soon as code and pretrained checkpoints are released. I am open to suggestions, let's use this thread to collect relevant papers and code.

As a reference, but I don't think the code is available:
https://stableprojectorz.com/

As a reference, but I don't think the code is available: https://stableprojectorz.com/

As far as I can see this doesn't really do anything special, it allows you to stitch together multiple single projections by inpainting. This is already somewhat possible in the plugin with the Preserve Existing Texture Data checkbox. I'm more interested in full 3D texturing methods that account for mesh topology.

does this create a 2D UV texture based on a single input image?


Extend the Vault CRD with a configuration for credentials (aka service account)

This configuration can be used to mount a dedicated service account with the required roles only in the vault,unsealer and configurator containers.
Add a script which generates the boilerplate code for Vault CRD
Regenerate the boilerplate code

Hi @ccojocar, by " boilerplate code for Vault CRD" you mean an API client for Vault objects?

Right, and deep copy

I tested right now with GKE, and it works well.

Great! Could you please have look at the build, it has some issues with VaultList objects.

@bonifaido It seems that some of the code generated for the client was not compiling. The build is not green.

Now the build is fine, I will have a look at this soon. Thank you!!


How to style the suggestion popup

G'day,
I'm trying to use this component, but when I render it the popup appears to take the entire window width rather than conforming to the enveloping div.  Here's what it looks like rendered...

Any hints on whether this is a bug or is there a prop somewhere I can tweak to rest the style?

Its probably a bug/missing functionality. Do you have a snippet/repo that I can check out?

Just added you to the repo that has the client code... The component in question is /src/Component/PersonalDetails.jsx
Cheers!

Hi @andrewjdavison,
Thanks for access to the repo with the clientcode. So the problem isn't a bug but a lack of functionality that provides fine grained control over the appearance of <MUIPlacesAutocomplete>. There is a feature request filed to track this functionality that would allow fine grained control over the appearance: #29.
I've confirmed that this is indeed the issue as 1) if you change this line (https://github.com/Giners/mui-places-autocomplete/blob/master/src/MUIPlacesAutocomplete.jsx#L70) to read:
-        style={{ left: 0, right: 0, zIndex: 1 }}
+        style={{ left: 0, right: 0, zIndex: 1, width: 400 }}

You will see that the <div> element that holds the suggestions is modified and doesn't take the full width of the screen (which may be what you desire). Also, 2) there is no prop you can pass today to modify the appearance of the suggestions container as we have just done.
If you want to see this for yourself you can checkout this repo and make changes to <MUIPlacesAutocomplete> and then yarn build and then yarn demo.
I would love to resolve this for you and have you use <MUIPlacesAutocomplete>. Unfortunately I don't have much time at the moment otherwise I would have worked on #29 already. I'm starting a new job and am packing up the house to move in a couple of weeks.
I'll try to find a couple of hours to work on it this weekend. If I can't then I would be happy to help you find a replacement for <MUIPlacesAutocomplete> if you aren't able to wait.

Thanks very much. I might take a look at the code myself and see if I can’t
help you out.
Cheers,
Andy
On Thu, 28 Jun 2018 at 23:10, Chris Austin<EMAIL_ADDRESS>wrote:

Hi @andrewjdavison https://github.com/andrewjdavison,
Thanks for access to the repo with the clientcode. So the problem isn't a
bug but a lack of functionality that provides fine grained control over the
appearance of . There is a feature request filed
to track this functionality that would allow fine grained control over the
appearance: #29
https://github.com/Giners/mui-places-autocomplete/issues/29.
I've confirmed that this is indeed the issue as 1) if you change this line
(
https://github.com/Giners/mui-places-autocomplete/blob/master/src/MUIPlacesAutocomplete.jsx#L70)
to read:

   style={{ left: 0, right: 0, zIndex: 1 }}+        style={{ left: 0, right: 0, zIndex: 1, width: 400 }}

You will see that the  element that holds the suggestions is
modified and doesn't take the full width of the screen (which may be what
you desire). Also, 2) there is no prop you can pass today to modify the
appearance of the suggestions container as we have just done.
If you want to see this for yourself you can checkout this repo and make
changes to  and then yarn build and then yarn demo.
I would love to resolve this for you and have you use
. Unfortunately I don't have much time at the
moment otherwise I would have worked on #29
https://github.com/Giners/mui-places-autocomplete/issues/29 already.
I'm starting a new job and am packing up the house to move in a couple of
weeks.
I'll try to find a couple of hours to work on it this weekend. If I can't
then I would be happy to help you find a replacement for
 if you aren't able to wait.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Giners/mui-places-autocomplete/issues/40#issuecomment-401029066,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMsgNgoW0QjX1QMukRR1Tc2XgHC7Irfnks5uBNXagaJpZM4U35hK
.

If you could and wanted to open a PR that would be great. Let me know if you have any questions. We can collaborate on it and get it done probably pretty fast together. My thoughts with #29 was to use styling/withStyles() but this seems more complicated than it needs to be at the moment.
One thought would be to take a new prop named suggestionsContainerProps which would take an object with style properties you wanted to apply to the container that contains rendered suggestions. Its properties could then be spread on the line that I mentioned. Things "ought to work" after that.
Let me know if you take a crack at it and what you think.

Yeah, the latter was what I was thinking. I'll dig around and see what I
can get working over the weekend.
Andy
On Thu, Jun 28, 2018 at 11:48 PM Chris Austin<EMAIL_ADDRESS>wrote:

If you could and wanted to open a PR that would be great. Let me know if
you have any questions. We can collaborate on it and get it done probably
pretty fast together. My thoughts with #29
https://github.com/Giners/mui-places-autocomplete/issues/29 was to use
styling/withStyles() but this seems more complicated than it needs to be
at the moment.
One thought would be to take a new prop named suggestionsContainerProps
which would take an object with style properties you wanted to apply to the
container that contains rendered suggestions. Its properties could then be
spread on the line that I mentioned. Things "ought to work" after that.
Let me know if you take a crack at it and what you think.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Giners/mui-places-autocomplete/issues/40#issuecomment-401040832,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMsgNirc8NG9f7gyZucrOPexGQC_3p_Zks5uBN6QgaJpZM4U35hK
.

Hi @Giners and @andrewjdavison I've created a pull request https://github.com/Giners/mui-places-autocomplete/pull/41 to resolve this issue based upon the suggestionsContainerProps method mentioned above.

If I would like to style it in a way where the width wouldn't be 100% how would I do so?

Hi @yosefprogramming I raised pull request #41 for this feature however I've been unable to get a reply from @Giners for a few months now. I'll probably publish my fork to npm.

Hey @robinknox. Thanks would really be usefull. Also would appreciate if you let me know once you publish the fork.


Support usage of CpsTable

The only suggestion is to use
:root {
  --cps-mdoc-viewer-primary: var(--cps-color-calm);
  --cps-mdoc-viewer-secondary: var(--cps-color-prepared);
}

because of cps-table

Do you mean to align cps-table coloring with the primary and secondary color? I started doing it, but then realized, it would be more effective to first make cps-ui-kit support theming and then just use --cps-mdoc-viewer-primary/secondary in the theme.
By theming in the cps-ui-kit I mean something like we are doing in this library - let the users define primary/secondary color and use those colors and their shades in the components. We can implement that gradually, so once CpsTableComponent will support it, it can be updated in this library.

Do you mean to align cps-table coloring with the primary and secondary color? I started doing it, but then realized, it would be more effective to first make cps-ui-kit support theming and then just use --cps-mdoc-viewer-primary/secondary in the theme.
By theming in the cps-ui-kit I mean something like we are doing in this library - let the users define primary/secondary color and use those colors and their shades in the components. We can implement that gradually, so once CpsTableComponent will support it, it can be updated in this library.

I mean exactly what I wrote above:
in styles.scss use
:root {
  --cps-mdoc-viewer-primary: var(--cps-color-calm);
  --cps-mdoc-viewer-secondary: var(--cps-color-prepared);
}

Until cps-ui-kit will support custom colors (which is not going to happen soon), use --cps-color-calm and --cps-color-prepared as primary and secondary colors in this library example app.

ahaa, I see now, thanks for explaining, colors are replaced now


Example 2 - Replicating figure 5D from Momi et al., 2023

Varying inhibitory time constant (b) parameter, and seeing the effects on the TEPs.

The example needs to load a previously-fit whobpyt model.
It will generate a figure similar to this:


rtmpdump_gnutls: add missing lib nettle & use git date format

@vcunat @pSub
This was just changed recently to try an get rid of more instances of propagatedBuildInputs
https://github.com/NixOS/nixpkgs/commit/775c412e573fa405da130b93363c8f8bc1d9e0b3#diff-cff75ddd8906caa1da857c27ce0a660aR26

Yes, I see the drop of propagation was fine, as $[gnutls}/include/* don't mention nettle at all.


@orta => [Router] Fix error with disallowed chars in User-Agent.

I don’t know why there was a test that checked for the device name being included, I don’t see a need for it.
When including the device name, it could contain characters outside the allowed character set, which could lead to encoding issues on the backend. E.g.
Mozilla/5.0 Artsy-Mobile/2.3.0 Eigen/2015.10.15 Device: Eloy Durán’s iPod/2.3.0 (iPod touch; iOS 8.4.1; Scale/2.00)AppleWebKit/601.1.46 (KHTML, like Gecko)

Includes a unicode ’ and results in the following error on the https://stagingapi.artsy.net/api/v1/me/bidder_position endpoint:
Full error
irb(main):005:0> puts bt.reject { |s| s.include?('gems') }
/srv/www/gravity/releases/20151015140557/app/api/v1/me_bidder_positions_endpoint.rb:63:in `block (3 levels) in <class:MeBidderPositionsEndpoint>'
/srv/www/gravity/releases/20151015140557/lib/tale.rb:13:in `call'
/srv/www/gravity/releases/20151015140557/app/api/middleware/logger_middleware.rb:22:in `block in call'
/srv/www/gravity/releases/20151015140557/app/api/middleware/logger_middleware.rb:21:in `call'
/home/deploy/.bundler/gravity/ruby/2.0.0/bin/unicorn_rails:23:in `load'
/home/deploy/.bundler/gravity/ruby/2.0.0/bin/unicorn_rails:23:in `<main>'

/cc @mzikherman

The device gives all this stuff 2.3.0 (iPod touch; iOS 8.4.1; Scale/2.00)AppleWebKit/601.1.46 (KHTML, like Gecko) which we need. You could get the exact device name and remove it from the device string instead?

Can you explain why we need that? The test didn’t tell me why it’s important to have.

the website + it's libraries don't know anything about what the browser supports, so things like our fonts.com scripts break because it thinks its some rando browser, not webkit

But isn’t that what the ‘Mozilla/5.0’ and ‘AppleWebKit’ etc were added for? https://github.com/artsy/eigen/commit/2faf450837f8e561f315b4351aba8ba395279fc9

(Those are still there.)

Oh yeah, cool, if you've triple checked that this doesn't break fonts on martsy/force then it's totes mergable.

I have not :) I will do so now.

The User-Agent header now looks like:
Mozilla/5.0 Artsy-Mobile/2.3.0 Eigen/2015.10.15/2.3.0 (iPhone; iOS 9.0; Scale/2.00) AppleWebKit/601.1.46 (KHTML, like Gecko)

And font rendering works as expected:

Great job :+1:


Merge keystore dao to kernel core

Describe
This effort will move the keystore package from framework:security-mgt to the kernel:core. The decision has been taken to do so was due to a cyclic dependency between the keystore package and the keyStoreAdmin in carbon-core.
The effort includes the DAO layer implementation inrtroduced when removing registry implementation from keystore.
Related issues

https://github.com/wso2/product-is/issues/16422

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.5 out of 6 committers have signed the CLA.:white_check_mark: DilshanSenarath:white_check_mark: Kanapriya:white_check_mark: madurangasiriwardena:white_check_mark: ThumulaPerera:white_check_mark: mpmadhavig:x: wso2-jenkins-botYou have signed the CLA already but the status is still pending? Let us recheck it.

Merging as this only maintains in a feature branch.


Thin blue line under dark green area on CMS pages

On CMS pages only, there's a 1-pixel blue line under the hills/forest graphical element.

Closing, as the line has now switched over to the other side, see #543


How to create a par file  without maud

Hello,
I am working at the Soleil synchrotron and I need to generate a 'par' file  for xrd texture analysis after the azimuthal integration of a pilatus detector with the binoculars-ng program https://repo.or.cz/hkl.git. This program generate an hdf5 file and I just need to convert it.
thanks for your advices.
Frederic

Hello, Frederic,
have you tried the two synchrotron 2D diffraction tutorial papers by Rudy
Wenk, Luca, Lowell Myagi and others?
Sven
On Mon, May 6, 2024 at 3:26 AM picca @.***> wrote:

Hello,
I am working at the Soleil synchrotron and I need to generate a 'par' file
for xrd texture analysis after the azimuthal integration of a pilatus
detector with the binoculars-ng program https://repo.or.cz/hkl.git. This
program generate an hdf5 file and I just need to convert it.
thanks for your advices.
Frederic
—
Reply to this email directly, view it on GitHub
https://github.com/luttero/maud/issues/6, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFVFNLWECVHDMLPK44OA6LZA5EFTAVCNFSM6AAAAABHIV74B2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4DANBTGM3TAMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

----- Le 6 Mai 24, à 16:06, Sven Vogel @.*** a écrit :

Hello, Frederic,

Hello,

have you tried the two synchrotron 2D diffraction tutorial papers by Rudy
Wenk, Luca, Lowell Myagi and others?

No.
You have a pointer to the tutorial
I tried here[1] but did not found something relevant.
[1] https://luttero.github.io/maud/tutorials/

try these
Lutterotti, L., Vasin, R., & Wenk, H. R. (2014). Rietveld texture analysis
from synchrotron diffraction images. I. Calibration and basic analysis. Powder
Diffraction, 29(1), 76-84.
Wenk, H. R., Lutterotti, L., Kaercher, P., Kanitpanyacharoen, W., Miyagi,
L., & Vasin, R. (2014). Rietveld texture analysis from synchrotron
diffraction images. II. Complex multiphase materials and diamond anvil cell
experiments. Powder Diffraction, 29(3), 220-232.
On Mon, May 6, 2024 at 2:18 PM picca @.***> wrote:

----- Le 6 Mai 24, à 16:06, Sven Vogel @.*** a écrit :

Hello, Frederic,

Hello,

have you tried the two synchrotron 2D diffraction tutorial papers by
Rudy
Wenk, Luca, Lowell Myagi and others?

No.
You have a pointer to the tutorial
I tried here[1] but did not found something relevant.
[1] https://luttero.github.io/maud/tutorials/
—
Reply to this email directly, view it on GitHub
https://github.com/luttero/maud/issues/6#issuecomment-2096834279, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFVFNO6ZSBABRGCAJIH5WTZA7QSPAVCNFSM6AAAAABHIV74B2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJWHAZTIMRXHE
.
You are receiving this because you commented.Message ID:
@.***>

try these
Lutterotti, L., Vasin, R., & Wenk, H. R. (2014). Rietveld texture analysis
from synchrotron diffraction images. I. Calibration and basic analysis. Powder
Diffraction, 29(1), 76-84.
Wenk, H. R., Lutterotti, L., Kaercher, P., Kanitpanyacharoen, W., Miyagi,
L., & Vasin, R. (2014). Rietveld texture analysis from synchrotron
diffraction images. II. Complex multiphase materials and diamond anvil cell
experiments. Powder Diffraction, 29(3), 220-232.

thanks a lot, for theses scientific articles :).
but  I want to create MAUD par files from my binoculars-ng program in order to do the data analysis via MAUD.
Do you have somewhere a description of your par format ?
So I could write  a programm which allows to export in the MAUD format.
thanks
Frederic

That is probably most easily done with MILK
https://github.com/lanl/MILK
Make a template manually once, then use your data and MILK to modify?
On Tue, May 7, 2024 at 2:36 AM picca @.***> wrote:

try these
Lutterotti, L., Vasin, R., & Wenk, H. R. (2014). Rietveld texture
analysis
from synchrotron diffraction images. I. Calibration and basic analysis.
Powder
Diffraction, 29(1), 76-84.
Wenk, H. R., Lutterotti, L., Kaercher, P., Kanitpanyacharoen, W., Miyagi,
L., & Vasin, R. (2014). Rietveld texture analysis from synchrotron
diffraction images. II. Complex multiphase materials and diamond anvil
cell
experiments. Powder Diffraction, 29(3), 220-232.

thanks a lot, for theses scientific articles :).
but I want to create MAUD par files from my binoculars-ng program in order
to do the data analysis via MAUD.
Do you have somewhere a description of your par format ?
So I could write a programm which allows to export in the MAUD format.
thanks
Frederic
—
Reply to this email directly, view it on GitHub
https://github.com/luttero/maud/issues/6#issuecomment-2097752551, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFVFNKARCYJUEH6H2H4XDDZBCG7HAVCNFSM6AAAAABHIV74B2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJXG42TENJVGE
.
You are receiving this because you commented.Message ID:
@.***>


Fix find API interface

Current find API interface is a little bit strange.

LGTM, but it alters the public interface. Should we mark this as non-compat?

These functions are not documented. It is very minor and, current implementation has some bug.

feature label is better.

Yes, I know it's not documented.
But it's been a while since it was introduced, so I concern some advanced users can be using it.
Also I think this change is not crucial for its functionality. I mean if we are going to be conservative, it's easy to keep compatibility and still implement a feature that uses it in stable branch.

OK, I understand your concern.
Cloud you merge as no-compatibility PR.

OK, I will not backport.
Btw, what is the bug you mentioned above?

LGTM!


Cannot delete None/Null values from table

Hi there,
calling table.drop({"column_name": None}) does not delete columns containing None values but the entire content of the table - see example below.
Furthermore, the documentation suggests that all rows are only deleted if the coordinates are None. However, as there is no distinction between None and 'falsy' coordinates in _java_api.py::delete_rows_from_table providing an empty mapping (i.e. table.drop({})) has the same effect. When deriving the coordinates dynamically that becomes an important detail 😉
Steps to reproduce
import atoti as tt
import pandas as pd

data = df = pd.DataFrame(
    columns=["City", "Price"],
    data=[
        ("London", 240.0),
        ("New York", 270.0),
        ("Paris", 200.0),
        ("Nantes", None),
        ("Frankfurt", None)
    ],
)

session = tt.Session()
table = session.read_pandas(data, table_name="data")

session.create_cube(table)
print(f"Price column is nullable: {table['Price'].data_type.nullable}")
table.head(20)

City
Price

London
240.0

New York
270.0

Paris
200.0

Nantes
NaN

Frankfurt
NaN

Let's try do delete entries with None/Null values:
table.drop({"Price": None}) # drops the table's entire data

Actual Result

| City | Price
-- | -- | --

Expected Result

City
Price

London
240.0

New York
270.0

Paris
200.0

Environment

atoti: 0.6.6
Python: 3.8.10
Operating System: Windows 10

Hi!
Indeed I can reproduce with the following code:
    import atoti as tt
    import pandas as pd

    data = pd.DataFrame(
        columns=["City", "Price"],
        data=[
            ("London", 240.0),
            ("New York", 270.0),
            ("Paris", 200.0),
            ("Nantes", None),
            ("Frankfurt", None),
        ],
    )

    session = tt.Session()
    table = session.read_pandas(data, table_name="data")

    table.drop({"Price": None})

We will work on it and let you know how when it is fixed. Many thanks for reporting it!

AP PR : https://github.com/activeviam/activepivot/pull/5242

Since this is waiting on an upstream development, for now we should raise a clear error on the Python side when one of the coordinates contains a None value.

Task list:

[ ] Raise NotImplementedError when dropping null values
[ ] Integrate AP development  that fixes the issue

Hello,
This will be fixed in the next release


Python regex warnings

You have to either escape string properly or use regex string literal (prepend string literal with r). Here is patch:
regex_fix.patch

I hope this problem is fixed with the latest release. Can you confirm?

Yes, no more warnings.


InvalidIdentityPoolConfigurationException: Invalid identity pool configuration. Check assigned IAM roles for this pool.

I keep getting the error in the above title. I found another issue with this same problem, but can't solve it. I've got an identity pool, 1 role (assigned to authenticated and unauthenticated) with the following trust settings
{   "Version": "2012-10-17",   "Statement": [     {       "Effect": "Allow",       "Principal": {         "Service": "lambda.amazonaws.com"       },       "Action": "sts:AssumeRole"     },     {       "Effect": "Allow",       "Principal": {         "Service": "lambda.amazonaws.com"       },       "Action": "sts:AssumeRoleWithWebIdentity"     },     {       "Effect": "Allow",       "Principal": {         "Service": "cognito-idp.amazonaws.com"       },       "Action": "sts:AssumeRoleWithWebIdentity"     },     {       "Effect": "Allow",       "Principal": {         "Federated": "cognito-identity.amazonaws.com"       },       "Action": "sts:AssumeRoleWithWebIdentity",       "Condition": {         "StringEquals": {           "cognito-identity.amazonaws.com:aud": "my-identity-pool-id"         },         "ForAnyValue:StringLike": {           "cognito-identity.amazonaws.com:amr": "authenticated"         }       }     }   ] }
The role has one policy attached
{     "Version": "2012-10-17",     "Statement": [         {             "Sid": "VisualEditor0",             "Effect": "Allow",             "Action": [                 "iam:*",                 "cognito-identity:*",                 "lambda:*",                 "mobileanalytics:PutEvents",                 "sts:*",                 "cognito-idp:*",                 "cognito-sync:*"             ],             "Resource": "*"         }     ] }
Gone for the "see what sticks" approach and so far, no luck. Am i missing something?
{ token: 'big-token-with-token_use-set-to-id', provider: 'cognito-idp.eu-west-1.amazonaws.com/user-pool-id', IdentityPoolId: 'identity-pool-id-same-as-above' }
This is the params object that gets passed into getCredentialsForIdentity() in a lambda function. Does the lambda functions IAM role need changing?

 When i posted it, it was all neatly whitespaced.

Had to delete the identities listed in the browse identities part of the identity pool.


[MRG] Cleanup skopt/parameter.py with docs and some minor changes

Added docs and some minor cosmetics.
Removed prior for now so that we can compare our results with a randomized search where we have some prior knowledge about the candidates. (I understand it might be useful but YAGNI)

@AlexanderFabisch @fabianp Since you have used the library to an extent, we would like to hear your thoughts on this. The idea is to support function calls like this at some point of time
gp_optimize(func, [Real(2, 4), ["red", "green"]])

bounds will be either a list of Distribution objects or lists. If it is a list of lists, then the type of parameter will be inferred.
(I am just cleaning up the work of @betatim done here https://github.com/scikit-optimize/scikit-optimize/pull/70)

That's a good idea. Here are some suggestions:

Maybe the argument name bounds is a little bit misleading for [Real(2, 4), ["red", "green"]]. You could introduce an additional argument param_distributions.
Real should actually be UniformReal. There could be NormalReal or LogReal as well like (similar to hyperopt).

However, my main focus at the moment is the optimization of real vectors so I actually don't really care about this use case.

By the way, is it possible to set a seed in scipy.stats distributions? It would be much better if you could simply pass a seed for the random number generator in the function call like in sklearn.

I would vote to keep it Real (hahaha...) and support non uniform priors via Real(..., prior=dist.norm(..)) or Real(..., prior=dist.exp(..)) etc. At least that was my thinking about having a prior parameter. What do you think?
To me it seems worth having the prior and the transform separate. The prior represents where you think likely good values are and the transform takes care of turning the values into something that is "ncie" for the optimiser to handle (onehot encoding, similar ranges)

Hi, thanks for the heads up.
I'm general I'm skeptical for the need of such framework (but I could be wrong). In the usercases I'm familiar with you never need more than to set bounds and/or optionally transform to logspace, so this might be overkill. I know RandomizedSearchCV takes a distribution argument, but I've never used it for anything else besides uniform sampling (sometimes in log space).

Thanks a lot for your feedback.
@fabianp By skeptical, are you skeptical about the use of priors or the support for categorical parameters? A common use case would be the type of scaling used or the kernel in SVM (I remember the paper on randomized search had something on those lines).
I also think it would be okay to support priors via arguments later.
@AlexanderFabisch Yes, we would pass a random seed to the function call which will then be passed internally to the rvs method and then sampled (as being done currently at https://github.com/scikit-optimize/scikit-optimize/blob/master/skopt/gp_opt.py#L121). Were you meaning this or something else?

@betatim Please review and if you are happy, do merge. In follow-up PR's I can address the remaining.

@AlexanderFabisch Yes, we would pass a random seed to the function call which will then be passed internally to the rvs method and then sampled (as being done currently at https://github.com/scikit-optimize/scikit-optimize/blob/master/skopt/gp_opt.py#L121). Were you meaning this or something else?

That is what I meant.

+1 for decoupling the domain/type of a variable (i.e., real, integer, categorical) from how it should be converted before being fed to the optimizer.
Overall, things should be very simple by default, e.g Real(2, 4)) (no transform, uniform distribution), but extendable in a plug and play manner with optional arguments, e.g. Real(2, 4, transformer="log", prior="gaussian").

Also I agree that we should start by having something very simple to begin with, i.e. supporting real integer and categorical types, all assumed to be uniformly distributed, with an optional log transform for the real values.

Is this ready for review? I am confused as this PR is adding parameter.py while parameters.py (with an s) is already there.

Could you instead base your PR on master? It is otherwise difficult to compare what you are actually changing. Not sure what was wrong with Tim's proposal.

There are still tests to be added.

Checkout the bug in the last commit :P

Woah! Thanks for catching this.

@glouppe @betatim
I'm slightly confused on the API of using  Real with say a log transformer vs using Categorical with a one-hot transformer. I would like to know your thoughts.
When using Categorical with a one-hot transformer, it makes sense to sample in the original space and then transform.
But when using Real it makes more sense to do this.
Original space: Bounds = (10**-5, 105)
Sample uniformly from (log10(10-5), log10(10**5)) = (-5, 5)
Raise to the power 10, when providing it to the optimizer.
That is sampling in the warped space, rather than the original space.

Does it make sense to do away with the transform method, and assume that rvs provides whatever needed, which can be directly fed to the optimizer? I believe it save us a lot of confusion. These are my proposed changes.
a = Real(0, 10)
a.rvs() # Sample uniformly from 0 to 10
a = Real(10**-5, 10**5, transformer="log10")
a.rvs() # log(Sample uniformly from -5 to 5)

a = Categorical(["a", "b", "c"], transformer="one-hot")
a.rvs() # One-hot-encode (randomly selected from ["a", "b", "c"])
a = LabelEncoder(["a", "b", "c"], transformer="label")
a.rvs() # LabelEncode (label encode randomly selected from ["a", "b", "c"]

Commenting again since the previous comment was hidden from the diff view.
Also does it make sense to remove the prior argument? Since giving a say gaussian or poisson (or anything other than uniform) prior makes the low and high values meaningless.

Two things:

The optimizer should operate in the warped space and be agnostic of that transformation. It is given bounds and points and proceed with that. No additional assumption are required.
We need decide on the definition of the prior, i.e. whether it concerns the original or the warped space. I am fine with i) deciding it concerns the warped space, ii) assuming a uniform prior by default.

Just to make sure that we are on the same page, do you agree that the current behaivour of using transformer="log" with prior="uniform" is incorrect?

The terminology is still not crystal clear to me.
Let us say alpha=(10**-5, 10**5), the warped space will be from (-5, 5).
It seems logical to sample from (-5, 5), raise it to the power of 10 and then provide it to the optimizer, no?
In that case the optimizer is not "operating in the warped space" right?

It seems logical to sample from (-5, 5), raise it to the power of 10 and then provide it to the optimizer, no?

No. I would feed values from (-5, 5) to the optimizer, and then use inverse_transform to convert back the found solution. Otherwise, you would still have these scaling issues at optimization.

Just to make sure that we are on the same page, do you agree that the current behaivour (output) whentransformer="log" is used with prior="uniform" for Real is incorrect?

If the prior concerns the warped space, as I suggest above, then it would just amount to uniformly space in log-space.

Great, I'll change it then.

My thinking behind splitting the prior and transformer was that there are two problems that need solving:

how to transform values that humans like (eg strings to label categories) to values that optimisers like (eg one hot encoded categories)
express how I believe the most likely/useful values of a parameter are distributed (eg gaussian around 5123 with std of 42)

Personally I find it easier to think about the prior in the original space and then let the computer transform it to the warped space for the optimiser: gauss(5123, std=42) plus StandardScaler() to get it to a sensible range for the optimiser. Maybe this is overkill/just my weird brain :)

Yes, which is why it makes sense to keep sampling in the warped space just for the uniform prior.

Proposal that could simplify things:
Let us hide the transform mechanism from the external API + Let define both "uniform" and "log-uniform" priors for Real.

 This is something internal and users should not deal with it.

We define two hardcoded priors for now, "uniform" and "log-uniform". In the later case, everything is done internally so that the optimizer deal with values in log-space, and then converted back to the original space.

@glouppe @betatim I've done as you have suggested. The tests should be the best way to understand the new API.

I have tried to keep the API as simple as possible.

I like where this is going :-)
On Jun 9, 2016 9:24 AM, "Manoj Kumar"<EMAIL_ADDRESS>wrote:

I have tried to keep the API as simple as possible.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/scikit-optimize/scikit-optimize/pull/75#issuecomment-224819602,
or mute the thread
https://github.com/notifications/unsubscribe/AAQ8h5sitgMXxrZgWXcFVka-WQtyYxiiks5qJ7-3gaJpZM4ItRTO
.

Thanks Manoj, this is looking good!
I think we should add a last test showcasing how non-trivial grids can be defined. E.g., by calling sample_points for grids defined in different but equivalent formats (e.g. Real(0, 1) and (0., 1.)) and checking for the same random_states, they yield the same points.

For ease of use, we should also accept triples for Real. That is:
(0., 1.) -> Real(0., 1., prior="uniform")
(0., 1., "log-uniform") -> Real(0., 1., prior="log-uniform")

All right, fixed both the inverse_transform and the tests. We can introduce the tuple shorthand in another PR. Please merge if happy

This is great, thank you! Waiting for Travis green light, and then I'll merge.

I'll address the shorthand.

Yay! We should also refactor the existing minimize code to make use of the new API.

I just made #81 with a few thrown ideas.

Whoop!


language/bad_raw_string_test/{03,none} failing when compiled by dartkp.

Message (see https://build.chromium.org/p/client.dart/builders/vm-kernel-precomp-linux-release-x64-2-4-be/builds/968/steps/vm tests/logs/stdio):
FAILED: dartkp-dart_precompiled release_x64 language/bad_raw_string_test/03
Expected: Pass
Actual: MissingCompileTimeError
Compile-time error expected.
CommandOutput[dartk]:
CommandOutput[precompiler]:
CommandOutput[assemble]:
CommandOutput[remove_assembly]:

I'm skipping the test for $compiler=dartkp now, so please fix and reenable.

The test /03 may fail on linux and macos and pass on Windows, as noted in #28664
I don't know what would make the none case fail.

@peter-ahe-google Is dartk still a going concern?

@peter-ahe-google I'm working on getting more gardening issues assigned. If you're not the right person to assign this to, please reassign to that person.

Thank you @nex3, I'll take a look.

Proposed "fix": https://codereview.chromium.org/2743943002


[LiveComponent] LiveProps: writable instead of modifiable attribute

Q
A

Bug fix?
no

New feature?
no

Tickets

License
MIT

I read the whole documentation on Twig Component and Live Component (thanks ❤!) and found a small typo. Well, I think it's a typo as I don't already tested the component :)

Good catch, thanks @gido.


Can't remove Node Pool using deployment-manager

Hi Everybody.
How to delete node pool with deployments-manager ? I did try the following:
delete the pool from .yml file, the gcloud deployment-manager deployments update this did not work and threw an error InputMapping for field [name] for method [delete] could not be set from input, mapping was: [$.concat($.resource.properties.parent, "/clusters/", $.ifNull($.resource.properties.name, $.resource.name), "/nodePools/", $.getElement($.resource.previous.cluster.nodePools, $.matches[0], "name"))
deleted finally the old node pool from WEB console manually and afterwards from .yml file, but now cant’ update anyting with deployment-manager at all

https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/issues/441

Any updates, I got the same issue as well.


XLM transfer successful but not showing up in Lobstr Wallet

Sent about 217 XLM to Lobstr and it shows it recieved but doesnt appear in my account. Please help as soon as possible. Thank you!

Did you get it

yes, i did thank you
On Fri, Apr 16, 2021 at 11:40 PM tlimberiou @.***>
wrote:

Did you get it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stellar-expert/stellar-expert-explorer/issues/410#issuecomment-821771255,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATT2VRUIOYOL3ECVBZIZT5LTJENLVANCNFSM42W5SL5Q
.

How? My xlm disappeared when I sent it to my other account In January still haven’t been able to recover it

Sorry to hear that and hope you get it fixed somehow. It was just very
delayed but it eventually just appeared in my account. I would try reaching
out to their support if you can.
On Fri, Apr 16, 2021 at 11:48 PM tlimberiou @.***>
wrote:

How? My xlm disappeared when I sent it to my other account In January
still haven’t been able to recover it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stellar-expert/stellar-expert-explorer/issues/410#issuecomment-821772095,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATT2VRUPVBAH7HVZUOTZSQTTJEOMVANCNFSM42W5SL5Q
.

Please help ,i transferred Xlm to right address but not arrived


ISO date -> hex seems wrong

Not sure E-notation in hex format is allowed.

its going ISODate => unix timestamp => Hex

is there a . in there?

Gotcha, right. Without sub-second works: https://eserialize.com/?input=string&output=hex&value=2019-12-24T15%3A39%3A45Z
Maybe we want a visible error there?


π looks like e

I think π ended up as an alternative in the wrong rule in the grammar.

Thanks so much, @Roenbaeck for noticing this.
I have update it, I hope it looks good.

Looks good!