28 Matching Annotations
  1. Jan 2020
  2. Nov 2019
    1. indexNo can be used along with fileName to generate a unique file name (e.g., fileName.indexNo) that you can use for the PF component file storing the new index.

      But what if a fileName has the form of fileName.indexNo?

    1. (* note implicit destruct here *)

      Be careful! There're two kinds of [destruct], one could be used to hypothesis, one to goal. We can only [destruct] the existence proposition in context.

    2. Since applying a theorem with hypotheses to some goal has the effect of generating as many subgoals as there are hypotheses for that theorem, we can apply and_intro to achieve the same effect as split.

      Same effect, but redundant and boring.

  3. Oct 2019
    1. owever, because Coq's "decreasing analysis" is not very sophisticated, it is sometimes necessary to write functions in slightly unnatural ways.

      What unnatural ways?

    2. It is sometimes useful to invoke destruct inside a subgoal, generating yet more proof obligations. In this case, we use different kinds of bullets to mark goals on different "levels." For example:

      Looks like markdown

    1. Thus the end-to-end argument is not anabsolute rule, but rather a guideline that helps in application and protocol design analysis; onemust use some care to identify the end points to which the argument should be applied

      尽管这一节的标题叫作Identifying the ends,但其实它只在最后一句提了一下需要identifying the end points,作者甚至一句也没有写如何identify!

    2. Thus the end-to-end argument again: if theapplication level has to have a duplicate-suppressing mechanism anyway, that mechanism canalso suppress any duplicates generated inside the communication network, so the function can beomitted from that lower level

      为什么如果应用层有抑制复制机制,网络内部也会有呢?因为应用层是通过识别重复消息来抑制重复消息的!

    3. he use of encryption for application-level authentication and protection is complementary. Neither mechanism can satisfy bothrequirements completely.

      为什么这么说?不是很懂QAQ

    4. Clearly, some effort at the lower levels to improve network reliability can have asignificant effect on application performance. But the key idea here is that the lower levels neednot provide "perfect" reliability.

      Lower level当然需要一定的reliability,但perfect reliability是不必的:在我看来这完全是一句废话,correct but useless。我只需提问:现在的状态是perfect了嘛?现在我继续优化已经不会得到better performance了嘛?这样,你又该如何回答?

    5. t the careful file transferapplication must still counter the remaining threats, so it should still provide its own retries basedon an end-to-end checksum of the file. And if it does so, the extra effort expended in thecommunication system to provide a guarantee of reliable data transmission is only reducing thefrequency of retries by the file transfer application; it has no effect on inevitability or correctnessof the outcome, since correct file transmission is assured by the end-to-end checksum and retrywhether or not the data transmission system is especially reliable.

      至此这篇才提出了第一个具体而有力的end-to-end argument(我终于看懂这是什么意思了QAQ)

    6. The function in question can completely and correctly be implemented only with theknowledge and help of the application standing at the end points of the communicationsystem. Therefore, providing that questioned function as a feature of the communicationsystem itself is not possibl

      我并不理解这个therefore

  4. May 2019
    1. By “ignoring”, I mean these units are not considered during a particular forward or backward pass.

      This is not a clear statement. What does "or" mean? We priorly choose to dropout in the forward phase or backward phase? Or for every individual neuron, we can choose if it's considered at forward phase or backward phase?

  5. Sep 2018