
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Functions for singly controlled operations
Conceptual overview
The Q# language provides the
Controlledfunctor to control operations on quantum registers of arbitrary size. It is often conveinent, however, for operations to accept exactly one control qubit. For example,Controlled Xhas type(Qubit[], Qubit) => Unit is Adj + Ctl, allowing for an arbitrary number of control qubits, but the shorthandCNOThas type(Qubit, Qubit) => Unit is Adj + Ctl. This shorthand is especially useful together with combinator operations such asApplyToEachCA:ApplyToEachCA(CNOT, Zipped(controls, targets));Current status
For operations other than
X, no such shorthand may exist in general. For example, on a recent stream, @crazy4pi314 used the following snippet combiningApplyToEachCAwithIncrementByIntegerto count the Hamming weight of a control register:ApplyToEachCA( (Controlled IncrementByInteger)(_, (1, target)), Mapped(ConstantArray(1, _), controls), );In this example, mapping
ConstantArray(1, _)is needed to add another level of nesting tocontrols, and is only needed because(Controlled IncrementByInteger)(_, (1, target))has typeQubit[] => Unit is Adj + Ctl(that is, takes an arbitrary number of control qubits).User feedback
See above example from @crazy4pi314's stream at https://www.twitch.tv/crazy4pi314.
Proposal
New and modified functions, operations, and UDTs
Modifications to style guide
No modifications required. New functions in this proposal follow the pattern of
CControlled,ControlledOnInt, and so forth by exposing functor-like callables as ordinary functions.Impact of breaking changes
n / a
Examples
See above.
Relationship to Q# language feature proposals
n/a
Alternatives considered
[[c0], [c1], ...]by adding new array functions.Controlledfunctor. We could consider adopting language proposals such as bounded polymorphism to allow theControlledfunctor to accept either single qubits or arrays thereof.Open design questions and considerations
CCNOT)?The text was updated successfully, but these errors were encountered: