text:
Visually indicate project status

This PR introduces the feature of indicating the project status by color.

[X] Extend the project summary (#101)
[x] Show total sample count in view (#104)
[x] Set default color to grey (#102)
[x] Completed statuses are shown in green (#102)
[x] Failing QC is indicated in red (#102)

This is what it would look like with the following colors:
//$v-friendly-color: #2c9720;
//$v-error-indicator-color: #ed473b;

This is what it would look like with the following colors:
//$v-friendly-color: #2c9720;
//$v-error-indicator-color: #ed473b;

What is the color of the grey? It looks bluish to me 🤔

#cbd5e8 as suggested by color brewer 😄

Hi @KochTobi and @Steffengreiner
thanks for your great work! I am happy with how it currently looks. I updated the colors to make them more apparent.
Is it possible to center the sample count?

Hi @KochTobi and @Steffengreiner
thanks for your great work! I am happy with how it currently looks. I updated the colors to make them more apparent.
Is it possible to center the sample count?

I think it should be doable by adding text-align: center; to the css

Since created this PR I cannot approve this card maybe someone else of the @qbicsoftware/itss members could do that?

authors: KochTobi jenniferboedker


text:
transforms: true does not work

The release notes say that enableTransforms has been renamed to transforms. This does not seem to be true. transforms does not work while enableTransforms still work.

Hi @twinpiloot,
Could you provide some logs as i have no issue using transforms in the new version 6 of the task; i also kept enableTransforms as alias in v6 to simplify upgrade.
For previous versions the input name hasn't changed.

That's strange, could you share your the task configuration so that i can try to reproduce?

This is what I had. Could it be that you are using version 6.0.5 and I 6.0.4?

task: replacetokens@6
displayName: 'Tokenize Configuration files and PowerShell scripts'
inputs:
root: '$(Pipeline.Workspace)'
sources: |
**/.ps1
**/.json
encoding: 'auto'
addBOM: true
escape: 'off'
missingVarLog: 'error'
keepToken: false
tokenPrefix: '#{'
tokenSuffix: '}#'
transforms: true

The changes between 6.0.4 and 6.0.5 didn't change anything on inputs or transforms.
I've tested with this YAML and still it's working:
- task: replacetokens@6
  inputs:
    root: '$(Pipeline.Workspace)'
    sources: |
      **/issue-25/*.txt
    encoding: 'auto'
    addBOM: true
    escape: 'off'
    missingVarLog: error
    keepToken: false
    tokenPrefix: '#{'
    tokenSufix: '#{'
    transforms: true
    logLevel: debug

I though maybe it was the agent not understanding input aliases but you are using other aliases (root, sources, addBOM...) without issues.
Could you share a redacted log with system diagnostics enabled to see what are the inputs received by the task?
Also not that you should replace keepToken: false with missingVarAction: none

It works for me :-)

source: gharchive/issue

authors: kipusoep qetza twinpiloot

repo: qetza/replacetokens-task

license: MIT

license_type: permissive

license_source: github-api


text:
std -> furo

With this PR the furo theme is provided instead of the rtd's one.

Thank you Andrea!
I've done the correction and put you as reviewer.

source: gharchive/pull-request

repo: qibogang/qibolab


text:
每日推荐音乐功能无法使用

尽量每个 issue 只提一个 bug 或新功能
加载不出首页的每日推荐音乐
查看控制台可见错误信息
反馈 bug 需要的信息

客户端，win11 amd64

活了，可能是本地网络抽风


text:
Trouble with Silva 128 in classify-otus-experimental ?

I ran fragment insertion as seen in the tutorial. I used the Silva 128 provided tree and alignment. My insertion tree was created, and I filtered my feature table. However, once I get to the classify-otus-experimental step and use the Silva 128 consensus 7 level taxonomy, I get the following error:
Not all OTUs in the provided insertion tree have mappings in the provided reference taxonomy.
I am attaching my insertion tree.
Any help would be appreciated!
insertion-tree.qza.gz

Hi @Rkubinski - we provide support on the QIIME 2 Forum - https://forum.qiime2.org. Please post your question there, thanks!

authors: Rkubinski thermokarst


text:
Idea : Canned metadata formats / transformers

Improvement Description
Create some form of cookie cutter default formatter for new metadata types.
Current Behavior
Almost every qiime2 plugin wants to output some metadata format in some form, whether it be taxonomies, genes annotations or even just summary stats.
Proposed Behavior
But given how ubiquitous metadata types are, it maybe worthwhile to design a cookie-cutter tools / templates to quickly flesh out transformers, formats for new metadata types.  Designing new metadata types is currently the bottleneck for my upcoming plugins and I imagine that this is the main hurdle for new q2 developers.  It could be as simple as creating a new plugin.register_metadata_type or something like that that auto-generates all of the relevant formats / transformers.

I agree, making some kind of base class for generic dataframe-like formats would make sense and reduce some boilerplate for defining new semantic types.
Just to comment quickly on some of your comments:

whether it be taxonomies

FeatureData[Taxonomy] should be used for such outputs

genes annotations

for generic annotations (e.g., mapping sequence IDs to an annotation) this could already probably output as FeatureData[Taxonomy]. We are working on defining new types/formats for gene and genome annotations specifically, so more on that soon.

I gave the Taxonomy type as an example, since it is already a slick metadata type.
But there are many others, such as the DADA2Stats or the SongbirdStats types.  I just pushed in a new type I called Matching, just so that I could append a new column to my metadata table.
Given how prolific these sort of types are there is much potential to save a substantial amound of developer time in the future with a unified data-frame type.

I really like this.
This topic just came up within a discussion with @mortonjt that one of the possible problem of creating more types is that developers will forget to create/add transformers (like this: https://github.com/flatironinstitute/q2-matchmaker/issues/31) and it seems like a lot of duplication of code. In specific, the matching example above is really similar to the alpha diversity results.

I think the ImmutableMetadata semantic type covers this now. Basically, as long as a file could be loaded into a qiime2.Metadata object, it can be output with semantic type ImmutableMetadata. This could then be used anywhere a metadata file could be used (e.g., qiime metadata tabulate) or exported to .tsv.
Closing this, but let me know if this doesn't capture what you're going for.

authors: antgonza gregcaporaso mortonjt nbokulich

license_source: bigquery


text:
库没法引用

Error:(47, 13) Failed to resolve: com.qindachang:BluetoothLELibrary:0.1.0
Show in FileShow in Project Structure dialog

不好意思，是jcenter审核问题。你可以先下载项目文件，通过import model的方式导入library。或者等待明天审核没问题再试试。有什么问题可以直接找我：Q 714275846

库已经可以正常引入，注意将minSdkVersion 设置为 18 以上哦

repo: qindachang/BluetoothLELibrary


text:
hash类型key太长显示问题

OS
Windows 11 22H2 22621.521
VERSION
1.5.8
ISSUE DESCRIPTION
list类型里如果value值太长就会只显示一部分加上省略号，鼠标放上去显示完整的value。
如何让hash类型里的key也可以那样显示？

好家伙，key是真长啊，我设想的是key都不会太长，所以设置的固定宽度，我看怎么兼容一下

改成和value一样了

authors: WHFo qishibo

repo: qishibo/AnotherRedisDesktopManager


text:
Added code to create session to match provider when running on a real device

Without added code, the wrong provider is used when submitting the job to real devices.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant attp


text:
Deprecate encoding.offset while incorporating it into encoding.qubit_op

Summary
Currently, the encode() method results in the operator being spanned across two properties: the traceless part is stored in qubit_op, while the constant offset is stored in offset.  The current separation follows the practice of to_ising() is Qiskit Optimization.  However, this separation seems unnecessary.  It conceptually simplifies things to store the operator entirely in qubit_op, as this PR proposes.
Details and comments
This will aid in solving #8 and with #9 (via the corresponding PR, #13).

There was some concern previously that storing the identity term within the operator might lead to additional quantum experiments being performed.  However, I have convinced myself now that this is not the case, so I'd like to move forward with this PR.
Here's why: Any reasonable implementation of an Estimator -- including the one in BackendEstimator -- is going to call group_commuting (which was introduced in Qiskit Terra 0.21) on the observables before sending them off to hardware.  Since the identity term commutes with everything, it will never lead to an additional experiment being performed.  There is the corner case where there are no other operators, and in that case could cause one experiment to be performed rather than zero, but that corner case is not of interest to us in QRAO.

repo: qiskit-community/prototype-qrao


text:
目录栏出现 0.1. 这样的字符如何去掉？

如图

已解决。

license: mit


text:
Test Issue - psjbg

Test Body - qsyrhgtegk

Test Comment - ezirq

repo: qlikqaa/dummyrepo


text:
Test Issue - fahfs

Test Body - btkqgpmyjp

Test Comment - bqccf


text:
Test Issue - vajbz

Test Body - wukoavwfzb

Test Comment - qsqnt


text:
Test Issue - ribbk

Test Body - wbtpkbzomq

Test Comment - sykmp


text:
Test Issue - dloxj

Test Body - pwfusjvofi

Test Comment - bouwx


text:
Test Issue - jhimv

Test Body - odpamigrrz

Test Comment - hcdlo


text:
Test Issue - rchab

Test Body - gwmuqdedzw

Test Comment - orpuu


text:
Test Issue - jcpbr

Test Body - rnefmyjxpl

Test Comment - qbasi


text:
Test Issue - zlbvg

Test Body - annqfendix

Test Comment - eacdn


text:
Test Issue - ekiau

Test Body - bdwhakmsue

Test Comment - chuif


text:
Test Issue - fvnhz

Test Body - dcrgnhcnyq

Test Comment - udzzc


text:
Test Issue - mqyvh

Test Body - oxktxyglcs

Test Comment - zjwvv


text:
Test Issue - bgtiy

Test Body - klqymitrkg

Test Comment - nieeb


text:
Test Issue - xrwlo

Test Body - qvzzzhcday

Test Comment - dhxck


text:
Test Issue - fxewj

Test Body - hnqmgyazfl

Test Comment - moiyk


text:
Test Issue - mzrif

Test Body - diozpzpykr

Test Comment - ypwgh


text:
Test Issue - njwle

Test Body - beqjvvdech

Test Comment - utumt


text:
Test Issue - bolnw

Test Body - zyrwhiulcf

Test Comment - sdkeu


text:
Test Issue - gccyt

Test Body - haxqlcfqgg

Test Comment - ryihy


text:
Test Issue - ybnme

Test Body - tioplkugwa

Test Comment - vddlf


text:
Test Issue - pklde

Test Body - ornvyuuchz

Test Comment - lsnnt


text:
Test Issue - lqfgn

Test Body - wpayxdxfhr

Test Comment - hkkbz


text:
Test Issue - akhyf

Test Body - lpqoncynts

Test Comment - sgfgx


text:
Test Issue - sxgzp

Test Body - whnbvjxtyr

Test Comment - flymq


text:
Test Issue - unojl

Test Body - uyrpslfijb

Test Comment - dmhlu


text:
Test Issue - jrcnz

Test Body - fzdmbanwtz

Test Comment - ixawn


text:
Test Issue - gwaqx

Test Body - tpkmgzqlkm

Test Comment - wkdzq


text:
Test Issue - qevzl

Test Body - dmthqkbfce

Test Comment - lugci


text:
Test Issue - fthpu

Test Body - hirruvhgkq

Test Comment - pcfof


text:
Test Issue - txtjn

Test Body - imvuzqavzh

Test Comment - uwcgz


text:
Test Issue - yjrzh

Test Body - eneogevuud

Test Comment - zjtav


text:
Test Issue - nobka

Test Body - zmzeinkyln

Test Comment - fkscx


text:
chore(metrics): Export RDS Certificate Authority attributes

The CA identifier is exposed as ca_certificate_identifier attribute of the rds_instance_info metric
The Unix timestamp of the expiration date of the CA certificate is exposed in the rds_ca_certificate_valid_until gauge.

For the rds-ca-2019 RDS CA, values are:
rds_instance_info{aws_account_id="012345678901",aws_region="eu-west-1",ca_certificate_identifier="rds-ca-2019",dbidentifier="rds-1",...}
rds_ca_certificate_valid_until{aws_account_id="012345678901",aws_region="eu-west-1",dbidentifier="rds-1"} 1.72434653e+09

#sre

PR updated to include 2 commits : 1 for each attribute.

repo: qonto/prometheus-rds-exporter


text:
Error 1170: BLOB/TEXT column 'key' used in key specification without a key length

I use
"go version go1.13.5 darwin/amd64"
"mysql  Ver 8.0.18 for macos10.14 on x86_64 (MySQL Community Server - GPL)"
After running "go run main.go"
it reports "[info] registering callback publish:versions from /path/to/go/src/github.com/qor/publish2/callbacks.go:77"
Failed to create unique index for translations key & locale, got: Error 1170: BLOB/TEXT column 'key' used in key specification without a key length
(/path/to/go/src/github.com/qor/i18n/backends/database/database.go:20)
[2020-01-02 11:58:26]  Error 1170: BLOB/TEXT column 'key' used in key specification without a key length

I have this same problem, leads to follow on problems and prevents me from using QOR Example

Same Issue, any updates?

authors: DanielJefferson1990 MukulLatiyan ctlaux

repo: qor/qor-example


text:
Framerate performance drop: commit #6

9ef8628f8583bc7494eeab1519f2ef2dd16fff0d
Hi, thanks for the awesome repo. :grinning:
I am currently using this repo to process video, and I noticed that commit #6 caused the framerate to drop by 1/3 on average as compared to commit #5. Is it because of the ZeroPadding2D fix?

I did a test roughly, and the time to detect one image is almost the same.
The revision does not increase the calculation. Check the input size of preprocessed image and see if two versions have difference.

Hi qqwweee, nice work!
I'm wondering what frame rate do you get? When I run this repo I cannot get anywhere close to the performance of original implementation of YOLOv3. Is it even possible to reach similar speed with keras?

I am working on GPU Tesla K40m. The original C version runs at 0.1s per image, the keras version 0.2s.
C is faster than Python (tensorflow or keras). But I do not know how big this gap is, and how to narrow the gap.

@qqwweee
Actually yolo_vide.py capture image via opencv an conver cv2 to PILonce the detection is done, then convert PIL to cv2. This work reduce a frame rate a bit, but not so much.
This is not the ideal solution but the easiest way to speed  up is to change BICUBIC to LINEAR ( resizing method)

authors: elliotwutingfeng qqwweee tanakataiki xxmarl


text:
🛑 otakusan is down

In bda873a, otakusan (https://otakusan.net/LightNovel) was down:

HTTP code: 0
Response time: 0 ms

Resolved: otakusan is back up in e891ed7 after 13 minutes.


text:
🛑 Xemphim club is down

In 46814de, Xemphim club (https://xemphim.club/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Xemphim club is back up in a9ab19e.


text:
🛑 otakusan is down

In f69d0c2, otakusan (https://otakusan.net/LightNovel) was down:

HTTP code: 0
Response time: 0 ms

Resolved: otakusan is back up in 8bf8999.


text:
🛑 medium is down

In 73afd73, medium (https://medium.com/) was down:

HTTP code: 429
Response time: 65 ms

Resolved: medium is back up in 57d5ceb.


text:
🛑 hako.re is down

In 8f3ee3e, hako.re (https://mangochan.site/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: hako.re is back up in 6af38b8.


text:
🛑 kokocon is down

In cffbaa7, kokocon (http://kokocon.net/) was down:

HTTP code: 500
Response time: 253 ms

Resolved: kokocon is back up in fa37eab after 7 minutes.


text:
🛑 otakusan is down

In e17d3ab, otakusan (https://otakusan.net/LightNovel) was down:

HTTP code: 0
Response time: 0 ms

Resolved: otakusan is back up in b63a643.


text:
Pandas requirement out of date

Dear Zipline Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment
Conda py3.6

Operating System: (Windows Version or $ uname --all) Ubuntu 16.04
Python Version: $ python --version3.6
Python Bitness: $ python -c 'import math, sys;print(int(math.log(sys.maxsize + 1, 2) + 1))'
How did you install Zipline: (pip, conda, or other (please explain)) Pip master into a condae nv with pyfolio maser
Python packages: $ pip freeze or $ conda list

Now that you know a little about me, let me tell you about the issue I am
having:
Description of Issue
Zipline down graded a number of packages including pandas from 20.2 to 18.. this prevents pyfolio from running,, so upgrading back to pandas 20.2 exposes no more pandas tslib.. it is gone so
an attempt to run from the example ipynb gives
%matplotlib inline
%load_ext zipline
/home/tom/anaconda3/envs/pyfolioenv/lib/python3.6/site-packages/zipline/utils/calendars/exchange_calendar_ice.py:10: FutureWarning: The pandas.tslib module is deprecated and will be removed in a future version.
  from pandas.tslib import Timestamp

Followed by:
     20 from six import string_types
     21 from sqlalchemy import create_engine

ImportError: cannot import name 'normalize_date'

What did you expect to happen?
What happened instead?

Here is how you can reproduce this issue on your machine:
Reproduction Steps

...
What steps have you taken to resolve this already?
...
Anything else?
...
Sincerely,
$ whoami

Hi @dartdog thanks for posting your issue. So there's a few things going on here:

Zipline does indeed require pandas 0.18, so upgrading to a newer version of pandas will not fix the issue as we don't yet support the newer version of pandas in zipline.
We don't support Python 3.6 for zipline so there may be issues from you running Python 3.6 as well

I suggest that you use zipline in a separate virtualenv from pyfolio if you want to use both of them.

@FreddieV4 Hi FreddieV4, I am trying to use zipline with pyforlio.
you suggest here "use zipline in a separate virtualenv from pyfolio if you want to use both of them."
Do you mean I need to switch between virtualenvs when I run code with both pyfolio and zipline?

xref https://github.com/quantopian/pyfolio/issues/407

Hi @Jfeng3 - as of now, you'll need to do that, because they don't currently work in the same virtual env. This is on our radar to fix in the short term.

Any news on this? It's a shame they don't work together.

Hi @aking7 , I believe pyfolio is compatible with pandas 0.18 again! Have you tried installing pyfolio from github to get the latest?
@twiecki Shall we cut a pyfolio release?

@richafrank I'm more interested in getting zipline up to date with the current pandas as I'm using some of its features.

@richafrank Definitely, should cut a new release.

@aking7 Ah, ok. I believe that was in progress here, but has been dormant for a bit. If you want to get a PR into a good state for the version you need, we can help shepherd it through.

Any progress on the new pandas (current 0.21.1)??

@imkoukou I'm not aware of any work done on zipline to support the latest pandas. PRs welcome!

So is there a way to reproduce the example found at
https://github.com/quantopian/research_public/blob/master/blog/bayes_opt/Blog_Post_Zipline_SigOpt.ipynb
If so, which version of pandas, zipline and pyfolio packages should one maintain in an environment?

Just ran into this and using the docker setup so using different virtualenvs gets pretty meta in my situation. Though admittedly I haven't tried setting up a 2x virualenvs within the docker containers. could be a fun experiment...
In general finding, the dependency tangles pretty gnarly. I wanted to update sklearn (cool new preprocessors!) and now wondering down a multi-day journey of reconfiguring my environment.

Hi. I'm Japanese boy.
I want to use it in google colaboratory, but I am suffering from this problem.
How many versions of pandas should I downgrade?

Closing - See https://github.com/quantopian/zipline/pull/2194 and https://github.com/quantopian/zipline/issues/2243

repo: quantopian/zipline


text:
Why the installed zipline can not be shown?

Dear Zipline Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment

Operating System: Windows 7
Python Version: 3.5.4
Python Bitness:
How did you install Zipline: conda install -c Quantopian zipline
Python packages: The list is too long to post here

Now that you know a little about me, let me tell you about the issue I am
having:
Description of Issue
I've just created a Python 3.5 environment under Anaconda 4. Then I install the zipline and it tells successful as follow:
zipline-1.1.1- 100% |###############################| Time: 0:00:00   1.48 MB/s
But as I check with 'conda search --full-name zipline', I get the following messages:
...
PackageNotFoundError: Packages missing in current channels:

zipline

We have searched for the packages in the following channels:

https://repo.continuum.io/pkgs/free/win-64
https://repo.continuum.io/pkgs/free/noarch
https://repo.continuum.io/pkgs/r/win-64
https://repo.continuum.io/pkgs/r/noarch
https://repo.continuum.io/pkgs/pro/win-64
https://repo.continuum.io/pkgs/pro/noarch
https://repo.continuum.io/pkgs/msys2/win-64
https://repo.continuum.io/pkgs/msys2/noarch

Why?

What did you expect to happen?
The installed zipline version should be shown.

What happened instead?
Zipline not found.

Here is how you can reproduce this issue on your machine:
Reproduction Steps
conda search --full-name zipline
What steps have you taken to resolve this already?
No idea.
Anything else?
...
Sincerely,
Thomas

Hi Thomas,
I'm not 100% certain, but I believe conda search is searching the anconda package index in the default channel(s), and there are no zipline packages in those channels. To add the quantopian channel to your search, you'd run:
$ conda search --full-name zipline -c quantopian

conda list should show the packages installed in your current conda environment.

@richafrank
this works. Many thanks.
$ conda search --full-name zipline -c quantopian

Great!


text:
Kedro viz & kedro run --parallel don't work when working with Spark

Description
Kedro viz doesn't work when I follow the Working with PySpark
 tutorial
Context
I'd like to use Spark session in my nodes to retrieve some data from my snowflake database. So, I followed the tutorial to initialize a SparkSession under __init__ in run.py. It seems like kedro viz doesn't like me to initialize a SparkSession  under __init__. I have to comment out self.init_spark_session() in order to run kedro viz.
Similarly, when I init SparkSession under __init__ in run.py, I got the same error message when I run kedro run --parallel.
Where should I do init_spark_session() except in the __init__ under, class ProjectContext,in run.py?
In addition, I am wondering what is the best practice to pass in a SparkSession in my nodes? What I did is to add a parameter in the create_pipelines method:
create_pipelines(spark: SparkSession, **kwargs)
Steps to Reproduce

Follow the Working with PySpark
 tutorial
Run kedro viz under terminal

Actual Result
Running Kedro viz or kedro run --parallel will give us the error message:
Error: It appears that you are attempting to reference SparkContext from a broadcast variable, action, or transformation. SparkContext can only be used on the driver, not in code that it run on workers. For more information, see SPARK-5063.
Your Environment
Include as many relevant details about the environment in which you experienced the bug:

Kedro version used (pip show kedro or kedro -V): 0.15.9
Python version used (python -V): 3.6.6
Operating system and version: Mac OS
Spark: 2.4.4

~~ Thank you so much for the help! Kedro is an awesome ML framework!

Hi @zhangchi1 Thank you for opening the issue! We were aware of this issue, and have fixed it in https://github.com/quantumblacklabs/kedro/commit/af39796ac5fa1ed904d9c82cb283e783011344d3 (it is still in dev and we will release it soon. Please have a look at the diff).
You could pass the spark session object from create_pipelines. Another way I can think of is to override _get_feed_dict from ProjectContext(KedroContext) in your run.py like below.
class ProjectContext(KedroContext):
     ....
    def _get_feed_dict(self):
           params = super()._get_feed_dict()
           params['spark_session'] = spark_session

This will be passed to your catalog, so you could refer to it in your node like
node(<node_func>, "spark_session", <output>)
Hope this helps :)

Hello Kiyohito, thank you so much for your reply.
Yes, I pass the spark_session from create_pipelines(self._spark_session). In order to serialize my nodes (I want to run kedro in parallel), I make my node as a class with a spark_session field. For example, I do my_nodes = ClassNode(spark_session) and func=my_nodes.my_funcin the pipeline. Do you think that's a good practice?
Right now, I'm able to run the project in sequential and run kedro viz with commented out self.init_spark_session(). So is that means I can run both kedro run --parallel and kedro viz in the next version release?
Again, thank you so much for your help~~

I assume you are referring to ParallelRunner? It does not work nicely with Spark, unfortunately, but we just added ThreadRunner in https://github.com/quantumblacklabs/kedro/commit/c79c21a50924b2f79f1207de167b27d7c7e8bef0 which would work with SparkDataSet (will be releasing in the next version).

Yes, I am talking about ParallelRunner. Thanks for pointing me to the updated docs kedro spark. At least, I can do kedro run now~~

You are welcome! I'm closing this issue, but feel free to reopen/ask us any more questions (we also have Stackoverflow https://stackoverflow.com/questions/tagged/kedro)!

repo: quantumblacklabs/kedro


text:
Produce LaTeX using qpic

I think the diagrams are nicer: https://github.com/qpic/qpic

It would be useful for someone to do a deep dive into qpic and list the advantages and disadvantages versus qcircuit.
One significant advantage to qpic is that it has an open source repo https://github.com/qpic/qpic so if we run into shortcomings we could contribute upstream.

Tracking this in #1492

authors: dabacon kevinsung

repo: quantumlib/Cirq


text:
Thermal noise model

This PR is part of #4640. It adds the ThermalNoiseModel, which models thermalization of a qubit - i.e., transitions from the |1) state to the |0) state or vice-versa, or dephasing events.
#4672 is a prerequisite for this PR. The only files that need to be reviewed in this PR are:

cirq-core/cirq/devices/...

__init__.py
thermal_noise_model[_test].py

Rebased and force-pushed to capture changes in the earlier PRs in this sequence.

Requesting input on @MichaelBroughton's comments from @dkafri, who wrote the internal version of this code. I could maybe stumble through the linear algebra here, but in particular I'd like to make sure we don't go against any decisions made in the original design of this model.

Comments have been addressed and this PR is ready for re-review.

Automerge cancelled: A status check is failing.

cirq-google/cirq_google/engine/engine_validator_test.py::test_create_gate_set_validator has a flake where the generated circuit is too long; testing shows this flake occurs ~0.4% of the time.
Opened #4796 to track this; re-running checks for now.


text:
Extract BufferedDM/SV/MPS from ActOnDM/SV/MPSArgs

Addresses #4827, cleaning up code by separating concerns between the quantum part and the classical part of density matrix / state vector / MPS sim state. (Clifford args are already factored like this). While it's a large PR, most of the change is just moving quantum-state-specific code from the ActOnArgs class, to a corresponding new quantum state class. This is done for DensityMatrix, StateVector, and MPS simulators. There are no behavioral changes in this PR.
As can be seen in this PR, this allows implementations of _on_kron, _on_factor, measure, etc. within ActOnArgs to be identical one-liners, delegating to the quantum state representation.
One particular thing to note here is that I have kept the initializers simple, just populating the member variables, and have created factory classmethods for more complex logic. This is because the quantum state representations need to support combinator logic like kron, factor, etc., and thus needs simple constructors that allow it to plug in the resulting member fields and move on. Having complex validation and transformation logic inside the constructor itself makes such combinators less efficient.
As a follow-up to this, I plan to create a common interface to enforce a standardization on these quantum state representations, and that will allow us to push some common logic into ActOnArgs base class. This will allow us eventually to deprecate the need for _on_kron etc handlers in each ActOnArgs entirely, and rely solely on the ActOnArgs base class doing this generically (see #5065).
For now I have kept these classes and any references to them private, but in consideration of #4582, we may eventually want to make these classes public and move them from sim into qis.

@95-martin-orion this is ready if you want to review. If it's too big I can break into pieces, but really it's just moving some code around, doing the same thing three times.
I added a fairly detailed description above.


text:
CI - deflake Isolated pytest Ubuntu

Problem: test_isolated_packages.py is still flaky and can fail on
parallel builds of a local cirq_core wheel.
Solution: Use per-worker copy of the cirq-core sources so that parallel
builds do not have conflicting build files.
Follow-up to #6593

ci-daily is passing for this PR at cad05ec029e1dbb2a6613327f5387dc574636f7b
https://github.com/quantumlib/Cirq/actions/runs/9107901404?pr=6603


text:
Add LinearCombination block encoding

Add an instance of BlockEncoding that builds a block encoding of the linear combination of its
constituent block encodings, given a list of coefficients.

The use case would be in case the user has more optimized oracles on hand. I think this is something @tanujkhattar mentioned as being useful.

repo: quantumlib/Qualtran