{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":96216817,"defaultBranch":"master","name":"jiveplot","ownerLogin":"haavee","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2017-07-04T12:39:32.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/14309703?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1689853286.0","currentOid":""},"activityList":{"items":[{"before":"3c025351c9e4e7ba51d52e9209c9bcb80717ff4c","after":"281e54f0b2fec7c17782bcec3ddba0eb523bfb12","ref":"refs/heads/master","pushedAt":"2024-02-02T14:34:00.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"haavee","name":"Marjolein Verkouter","path":"/haavee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14309703?s=80&v=4"},"commit":{"message":"Restore old default symbol scaling behaviour\n\nMarkK reports: w/ default settings usig only \"ptsz X\" symbols do not scale\nanymore?\n\nOld system worked by chance b/c the default symbol used to plot data (\"-2\")\ndoesn't scale with character height but with line width; old code set *both*\ncharacter height and line width when plotting symbols.\n\nNew behaviour was implemented:\ndrawing points set char size only, drawing lines set line width only.\ndefault symbol still \"-2\", so don't scale with \"ptsz X\" setting anymore.\nUser required to select different symbol (e.g. \"17\") for getting scaled data\npoints.\n\nThis is user unfriendly so this fix merges the two behaviours:\n- if symbol < 0 set line width to \"ptsz X\" setting before drawing\n- otherwise set character height\n\nDuring testing it was found that:\n symbol type=\n\n(e.g. to put back the old default symbol) didn't work: the regex didn't\nallow a leading minus sign (fixed).","shortMessageHtmlLink":"Restore old default symbol scaling behaviour"}},{"before":"622e69235e55aedac286f20385f53fcd9e8bb164","after":"3c025351c9e4e7ba51d52e9209c9bcb80717ff4c","ref":"refs/heads/master","pushedAt":"2023-07-20T11:41:14.000Z","pushType":"push","commitsCount":111,"pusher":{"login":"haavee","name":"Marjolein Verkouter","path":"/haavee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14309703?s=80&v=4"},"commit":{"message":"update readme to reflect master now Py2/Py3 compat","shortMessageHtmlLink":"update readme to reflect master now Py2/Py3 compat"}},{"before":"4161473a81fc4875f65e78662c758413f6960c4a","after":null,"ref":"refs/heads/control-c","pushedAt":"2023-07-20T11:20:53.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"haavee","name":"Marjolein Verkouter","path":"/haavee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14309703?s=80&v=4"}},{"before":"1cebb00dbea9a8a3fbafb1d78e96d4624d132a80","after":"126f991598934813d21569119e9f5f214ff9da42","ref":"refs/heads/new-master-#1","pushedAt":"2023-07-20T10:16:36.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"haavee","name":"Marjolein Verkouter","path":"/haavee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14309703?s=80&v=4"},"commit":{"message":"document optional '--force' flag to pl command","shortMessageHtmlLink":"document optional '--force' flag to pl command"}},{"before":"f7a49dc96b9cd748c030c36aa25d23871c09e02e","after":"1cebb00dbea9a8a3fbafb1d78e96d4624d132a80","ref":"refs/heads/new-master-#1","pushedAt":"2023-07-20T09:56:59.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"haavee","name":"Marjolein Verkouter","path":"/haavee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14309703?s=80&v=4"},"commit":{"message":"Merge branch 'control-c' into new-master-#1","shortMessageHtmlLink":"Merge branch 'control-c' into new-master-#1"}},{"before":"227d5109a92b460681d1f9230d642f06b681d8a1","after":"4161473a81fc4875f65e78662c758413f6960c4a","ref":"refs/heads/control-c","pushedAt":"2023-07-20T09:54:21.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"haavee","name":"Marjolein Verkouter","path":"/haavee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14309703?s=80&v=4"},"commit":{"message":"Do not print debug statement","shortMessageHtmlLink":"Do not print debug statement"}},{"before":"4ad574da063d309a195b8453254a9120723ad28d","after":"f7a49dc96b9cd748c030c36aa25d23871c09e02e","ref":"refs/heads/new-master-#1","pushedAt":"2023-04-11T13:58:16.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"haavee","name":"Marjolein Verkouter","path":"/haavee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14309703?s=80&v=4"},"commit":{"message":"remove debug print, add useful warnings\n\nWhen combining data sets using \"load X + Y\" or \"store 2*X / Y\" where both X\nand Y are sets of plots there are several possible (unexpected) outcomes and the s/w\nwould not inform you about *any* of them or whether they'd occurred. This is\nnow fixed.\n\nBackground: the syntax \"X Y\" triggers a combining function which\nwill apply the operator on the datasets in X and Y that have the same key -\nin pseudo-code:\n\n for key in intersect(X.keys(), Y.keys()):\n result[key] = operator(X[key], Y[key])\n\nNow, if X and Y do not have the same number of keys, or the keys differ\nbetween them, the number of keys in the result will be either 0 (no common\nkeys between X- and Y) or not equal to the number of keys in X or Y.\n\nThe software didn't use to check and just give you back \"result\", the\ncontent depending on the actual intersection of the sets of keys in X and\nthose in Y and not warn, ever.\n\nNow the code checks & warns for the different cases and issues an\nappropriate warning","shortMessageHtmlLink":"remove debug print, add useful warnings"}},{"before":"0ab5606b5319465f0b61a14574c4523fb43d1748","after":"4ad574da063d309a195b8453254a9120723ad28d","ref":"refs/heads/new-master-#1","pushedAt":"2023-04-11T11:20:00.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"haavee","name":"Marjolein Verkouter","path":"/haavee","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/14309703?s=80&v=4"},"commit":{"message":"fix erroneously raised unknown DATA_DESC_ID error\n\n The code was looking in all frequency groups and subbands defined therein to\n find a given DATA_DESC_ID but the handling of the returned result(s) was a\n bit too aggressive:\n\n if the requested DATA_DESC_ID was not found in the first result the code\n would raise an \"Invalid DATA_DESC_ID\" without checking other results first.\n\n This error should only be raised if all the returned results have been\n exhausted w/o finding a match (which it does now).\n\n There is one other intermediate check that currently throws an exception: in\n case > 1 spectral windows claim to be linked to the same DATA_DESC_IDs.\n In that case it is rather impossible to uniquely unmap a DATA_DESC_ID into a\n spectral window.","shortMessageHtmlLink":"fix erroneously raised unknown DATA_DESC_ID error"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAD8Er0QAA","startCursor":null,"endCursor":null}},"title":"Activity ยท haavee/jiveplot"}