W-Pettersson
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # WG multi-cops paper plan ## Deadlines - Larger changes by 12 noon on Thursday 16th - Small bugfixes/typos done by 9am Monday 20th - Will submits 5pm Monday 20th ## Plan All big changes by noon on Thursday. People read through and only make small changes after that, but before 9am Monday. 9am Monday Will takes what we have, and puts it into LNCS and starts putting things into appendices. No one else make changes directly, instead send Will an email with requested changes. ### What goes into the appendix Preferably list these in some sort of order ## Tasks ### Tasks to assign ### Jess - **Done** Introduction by noon on Thursday - **Done** Conclusion by noon on Thursday - **Done (by someone else? (sorry, WP just wrote that in. - Thanks!))** update below (p 21 green previously) - Treewidth has a known relationship with cop number: in particular, S&T use the helicopter variant of cops and robbers and show that the helicopter cop number of a graph is equal to ... We do not use this helicopter variant here. - Prints out PDF at noon on Thursday, reads what she can ### Will #### Before noon Thursday - **Done** Finish off tweaks to proof of Lemma 6.7 - cop number of cops-bane graph - **Done** Use multi-layer consistently - **Done** Use treewidth (no hyphens) consistently - **Done** (unless people have more ideas) Add simple results to end of Section 2 #### Monday 20th - 9am, start putting it into LNCS and moving into appendices - Submit by 5pm - Re-read on Tuesday morning for errors ### John - **Done** get rid of underscore Ds - change to 3-parameter notation - **Done** Binomial random graph section by Thursday noon - **Not Done, sorry** Related work? - **What is this? if relating to Random graph then done** New lower bound bit by Thursday noon # Things to discuss - The conclusion section is SUPER long, is that intentional? I am starting to get quite worried about the LNCS page limit. * JS I have condensed the recap bit and slightly reworded the questions (old one is commented out) - We define **k** = (k_1, ..., k_tau) as an allocation in our notation section, and use it to define our problems, but never use **k** in the rest of the paper but instead always say "allocation" as a full word. * WP in favor of leaving as is. * JS - same though it is a bit weird. # Resolved things - Binomial random graphs, Theorem 5.8. The statement says "n ≥ 1" but the proof often says "for large n". Which is it? * JS The fact the result only holds for large n is given by the $o(e^{-\sqrt{n}})$ etc. I would be happy to just delete the $n\geq 1$ it is just in the past I have been told off for not stating all the variables etc. * I think having "n ≥ 1" is misleading. I've tried writing it again without mentioning "n ≥ 1". **Done** - Theorem 5.8 again, the proof says "partition" often but I don't think that's what we want, as we don't want/need the layers to partition our graph. If this is just abusing terminology, then I don't like it as for WG I think they'll expect a partition to be a real partition. * JS agree but cant remember what we decided for this type of cock up, please change to prefered notion. * WP: Working on fixing this up. Last inappropriate uses of partition are just in the upper bound of Theorem 5.8, see below **Done** - Theorem 5.8 again again :) * WP: We don't clearly state why each layer is connected when doing our sampling. If $p > \ln n / n$ then almost surely they will be connected (do we need a citation?). From the theorem we have $n^{1/2+\varepsilon} ≤ np$ which (I hope) gives $n^{1/2 - \varepsilon} ≤ p$ and thus $p$ is clearly bigger than $\ln n / n$. * WP: For the upper bound, the proof is still correct if the layers aren't connected, but I wanted to avoid saying "partition". Instead, $G_{n,p}$ is connected - do we just need to say that each layer of $\mathcal{G}$ is exactly $G_{n,p}$ (rather than a partition)? I don't think this breaks anything. **Done this** * WP: For the lower bound, the bounding of $p^*$ means $p^*$ is also bigger than $\ln n / n$. Should we mention this? Just something like "Note the bound on p from the theorem statement ensures that each sampled graph will be connected." **Done this** * JS I forgot to add this sorry! Thanks for doing this, I tried to add a more detailed reference but could not find one that gives the exact prob I want $o(e^{-\sqrt{n}})$ although I am nearly certain this does hold. I might add a short proof. * WP So I know wikipedia is not a reliable source of information, but it does state that log n / n is a sharp threshold for connectedness of G_n,p - https://en.wikipedia.org/wiki/Erd%C5%91s%E2%80%93R%C3%A9nyi_model .. oooh I see. * Yes this is true, however I want it to hold with prob $1- e^{-\sqrt n}$ not just w.h.p.. I have now added a proof of this from base principals (Lemma 5.10) so we should be good to go! Thanks for spotting this! * WP Have you read through it and are okay with it yet? * I have just finished reading though the new lemma and old proof now and I think it is **Done** * P.s. I thought that putting $0\leq p\leq 1$ in the statement of Theorem 5.8 was weird if we dont also menton what $n$ is so I have taken this out and just specified n and p more clearly in the start of the section. - "Simple graph" vs "single-layer graph" vs "(single-layer) graph", also "(single-layer) cop number" and "(single-layer) cops and robbers". * WP doesn't like the brackets - "single-layer cops and robbers" makes sense and we can add a clarification sentence in the notation section * JS Simple has a concrete meaning in graph theory we should not abuse it, similarly I saw a "regular" somewhere to mean single layer and removed it. I don't care what is done with brackets. * WP Regular being mis-used is bad, but yeah simple does have a specific meaning, and all our "single-layer" graphs are actually simple graphs so it's at least a well-known definition. I think maybe a quick "As we discuss multi-player cops and robbers as well as cops and robbers played on simple graphs, we will use single-layer graphs to mean simple graphs, and then use single-layer cops and robbers to mean cops and robbers played on simple graphs (and similarly for terms like cop number)." * WP Standardised on "single-layer graphs" and "single-layer cops and robbers" etc, with one sentence in notation explaining this - Motivation of "global robber" idea, the text mentions "the robber not having an unfair advantage" * WP doesn't like talking about an "unfair advantage" because that really seems ambiguous. Can just drop that sentence and start with "A setting that appears often" * JS sure - Just after Lemma 5.1, "The definition and lemma above give simple to check criteria ..." * WP thinks simple is misleading. It's definitely not computationally "simple" i.e. tractable. * JS I did not mean simple to compute, just not hard to get head around. This is just a bit of careless chat separating two lemmas, feel free to change * WP Rephrased to avoid saying simple to check - Chatter around definition of minimum degree in multi-layer graphs (Just after Lemma 5.3) * WP still thinks we should be clearer that we are making up this definition, because it reads like this is an established definition already and it really isn't. Happy to leave discussion as-is though. * JS I have changed the text before it to indicate that it is a new parameter. * WP Looks good to me - Section 6.1. I get that our graphs have O(N log N) vertices and cop number at least omega(N). * WP: Are we sure that translates exactly to n vertices and theta(n / log n) cop number? It felt right at first glance, but when I sit down and try to work out intermediate steps I don't get anywhere near this. * JS the direction we really care about (\Omega bit) is super easy: N\log N =n , thus N < n (large n) so N = n/\log N > n/\log n. I cannot even see in the paper where we claim that it is \Theta(..)?? If we do we dont need to as nobody cares about the upper bound on that specific graph. Either way, here is the idea for the O() part: N=n/\log N = n/(\log n - \log\log N)\leq n/(\log n - \log\log n) < 2n/\log n when n is sufficently large. It is a bit less clean to do this formally but still elementary, this is why I left it out. * WP: Yup, that makes sense. And yeah, Omega not theta, sorry! - Section 6.1. We often state $\alpha > 0$, but rarely the $\alpha \leq 1$ part. * WP: Is there a reason to not always give both bounds? * Resolved - Conclusion * WP: Should we mention the possibility of multi-layer cops and robbers being useful for investigating interesting parameters for multi-layer graphs, the way cops and robbers is useful for treewidth etc. * JS yeh why not if we can write something nice * WP: have added a sentence for this # Things not in paper that can be looked at for a journal version, don't do now! - If R is a tree, and layers are connected, then mc(G) ≤ 2. If R is also a subset of some cop layer, then mc(G) = 1. However, it's O(tau^2) to work out if 2 cops can win in general, as you check every pair of layers for a robber's edge - Using a clustered 2-coloring of the line graph (max deg 4) of a three regular expander we can come up with a 2-edge-colouring of the expander such that each monochromatic component of edges has bounded size. This can then replace the 3-edge-colouring in the proof of Theorem 6.1, giving the same lower bound but usng one less cop layers.

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully