From d1f951ec232f333ab06302c3fc2005076426375b Mon Sep 17 00:00:00 2001 From: Julio Biason Date: Tue, 23 Jul 2024 17:07:21 -0300 Subject: [PATCH] vault backup: 2024-07-23 17:07:21 --- .obsidian/workspace.json | 40 ++++++-- .../2024-07-19 Core Foundation - Testing.md | 7 ++ Kanban Pages/HelyxVerify.md | 91 ++++++++++++------- 3 files changed, 96 insertions(+), 42 deletions(-) create mode 100644 Calendar/2024-07-19 Core Foundation - Testing.md diff --git a/.obsidian/workspace.json b/.obsidian/workspace.json index 0fb7ed0..5c979a2 100644 --- a/.obsidian/workspace.json +++ b/.obsidian/workspace.json @@ -8,18 +8,39 @@ "type": "tabs", "children": [ { - "id": "b0d5bcc79b7db544", + "id": "e0f7c14966a4e48a", + "type": "leaf", + "state": { + "type": "kanban", + "state": { + "file": "Kanban Pages/Work Kanban.md", + "kanbanViewState": { + "kanban-plugin": "board", + "list-collapse": [ + false, + false, + false, + false, + true + ] + } + } + } + }, + { + "id": "1d01cbb8a76aa34a", "type": "leaf", "state": { "type": "markdown", "state": { - "file": "Calendar/2024-07-18 Processes.md", + "file": "Kanban Pages/HelyxVerify.md", "mode": "source", "source": false } } } - ] + ], + "currentTab": 1 } ], "direction": "vertical" @@ -85,7 +106,7 @@ "state": { "type": "backlink", "state": { - "file": "Calendar/2024-07-18 Processes.md", + "file": "Kanban Pages/HelyxVerify.md", "collapseAll": true, "extraContext": false, "sortOrder": "alphabetical", @@ -102,7 +123,7 @@ "state": { "type": "outgoing-link", "state": { - "file": "Calendar/2024-07-18 Processes.md", + "file": "Kanban Pages/HelyxVerify.md", "linksCollapsed": false, "unlinkedCollapsed": true } @@ -125,7 +146,7 @@ "state": { "type": "outline", "state": { - "file": "Calendar/2024-07-18 Processes.md" + "file": "Kanban Pages/HelyxVerify.md" } } } @@ -147,9 +168,12 @@ "obsidian-full-calendar:Open Full Calendar": false } }, - "active": "b0d5bcc79b7db544", + "active": "1d01cbb8a76aa34a", "lastOpenFiles": [ + "Kanban Pages/Work Kanban.md", + "Kanban Pages/HelyxVerify.md", "Calendar/2024-07-18 Processes.md", + "Calendar/2024-07-19 Core Foundation - Testing.md", "Meetings/QA/2024-07-01.md", "Calendar/2024-07-01 QA.md", "Calendar/2024-06-24 DevOps Meeting.md", @@ -158,8 +182,6 @@ "Calendar", "2024-07-16 Terça Clã.md", "Untitled Kanban.md", - "Kanban Pages/HelyxVerify.md", - "Kanban Pages/Work Kanban.md", "BuildingTesting Pipeline.md", "Kanban Pages/ThirdPartyImage.md", "Kanban Pages/Teams Workflows.md", diff --git a/Calendar/2024-07-19 Core Foundation - Testing.md b/Calendar/2024-07-19 Core Foundation - Testing.md new file mode 100644 index 0000000..740e394 --- /dev/null +++ b/Calendar/2024-07-19 Core Foundation - Testing.md @@ -0,0 +1,7 @@ +--- +title: Core Foundation - Testing +allDay: true +date: 2024-07-19 +completed: null +--- +- Integrate both testing meetings (Core Foundation Testing and Testing) \ No newline at end of file diff --git a/Kanban Pages/HelyxVerify.md b/Kanban Pages/HelyxVerify.md index 1af2e64..07fb37b 100644 --- a/Kanban Pages/HelyxVerify.md +++ b/Kanban Pages/HelyxVerify.md @@ -36,10 +36,6 @@ # system/validationDict Idea for a Foam-formated file for Verify ```c++ -// List of variables to be checked; optional, since MD5 validation does not -// use any variables. -variables ("phi" "meanT"); - // Execution is run in sequence: If the first run ("quick") fails, then the // second run ("short") is run, and if that fails, the third is run ("long"), // and so on. On the other hand, the execution of the runs stops on the first @@ -59,17 +55,16 @@ variables ("phi" "meanT"); // so on. runs -( +​( // This is a quick test: The example is reduced to just 2 timesteps, and // we check the resulting file against its MD5 hash. - quick { + ​quick { steps 2; - generatedFile "postProcessing/2/blah"; - // because the validation is in MD5 format, there is no need to have - // a referenceFile - failIf { - md5Differs "123123"; - } + // Any other key name that it is not reserved ("steps", "continuations") + // represents a file to be compared. + "postProcessing/2/qux" { + md5 "123123"; + } } // In case the MD5 fails, the case is run again, but this time reduced to @@ -78,10 +73,6 @@ runs // will fail if relative or absolute differences are above 0. short { steps 10; - generatedFile "postProcessing/10/blah"; - referenceFile "verification/10/blah"; - // No tolerances mean "it will warn if the values are not the same" - // This makes the continuations explicit, by specificing files that // form a single run. continuations ( @@ -89,6 +80,17 @@ runs "system/caseSetupDict.continuation1" "system/caseSetupDict.continuation2" ); + "postProcessing/10/foo" { + reference "verification/10/foo"; + variables "phi" "Tmean"; + // No tolerances mean "it will fail if the values are not the same". + } + // This is a completely different file from the above, with different + // keys + "postProcessing/10/bar" { + reference "verification/10/bar"; + variables "Tmin" "Tmax"; + } } // If in 10 timestemps the values do not match the reference file, a 100 @@ -97,31 +99,32 @@ runs // threshold. long { steps 100; - generatedFile "postProcessing/100/blah"; - referenceFile "verification/100/blah"; - failIf { - absolute 10; - relative 10; - // will fail is the absolute difference is above 10 AND the - // relative difference is above 10; - operator and; + // This file only appears in the 100 runs, so we can't have a global + // list of files not attached to steps (although it is the same "foo" + // from 10 steps). + "postProcessing/100/foo" { + reference "verification/100/foo"; + variables "phi" "Tmean"; + } + "postProcessing/100/bar" { + reference "verification/100/bar"; + variables "Tmin" "Tmax"; } } // If the 100 timesteps fails, then we run the example a 4th time, this // time without any reductions (the "steps" property is not set in this // run). There are no continations either. - infinite { + "run till completion" { // With no steps, there is no reduction. - // (maybe we need something to tell that there is no reduction - // explicitly?) - generatedFile "postProcessing/20000/blah;" - referenceFile "verification/20000/blah"; - failIf { + "postProcessing/20000/baz" { + reference "verification/20000/baz"; + variables "integral"; absolute 20; relative 20; - // no operator means OR, so example will fail if the absolute - // different is above 20 OR the relative difference is above 20 + // no operator means OR, so example will fail if the + // absolute different is above 20 OR the relative + // difference is above 20. } } ); @@ -344,4 +347,26 @@ loop { - None: Complete - DictEnd: This dictionary is complete, return it - Anything else: -} \ No newline at end of file +} + +# Post lexer work + +- [ ] grep filter on expansion +- [ ] Runner with comparer + - Spawn tasks? How to join? + - Also, since the executor follows one run, and the comparer follow that run, does it matter using tasks? +- [x] Build "rundir" when loading Verification +- [ ] Variations?!?! + - Expand the whole case at the start. + - Load verification from expanded dirs. + - This is what the "Loader" was doing before, which I inadvertently merged with the verification loader. + - Order is mixed: The whole example can be expanded into their runs, but the execution is per non-expanded content (default, variations) + - Need to send, into the pipeline, the default, variations and the replicated Verification for each. + - Problem: The variation may contain different steps, anyway. So need to "expand" without having the verification info beforehand. + - What if: + - Expand default run into `.run-default` + - Expand variations into `.run-[variationname]` + - Inside each of those, expand the case (default won't expand, but still....) + - We could say it is not possible to add a new verificationDict into variations, but I do like the idea of having a different content for it. + - Ok, ignoring this for now 'cause it fucks up my thinking. + - Expand by run on default, send variations down the pipeline \ No newline at end of file