text:
[F Renderer.cpp:206] Check failed: std::isfinite((colors).mean().item())

use my custom data
python scripts/run.py --config-name=wanjinyou dataset_name=example case_name=outdoor mode=train +work_dir=$(pwd)
Working directory is /cephfs/yuanweizhong/project/f2-nerf
register Hash3DAnchoredInfo
register TCNNWPInfo
register volume render info
Aoligei!
[Dataset::Dataset] begin
Load render poses
[LoadImages] begin
[LoadImages] end in 17.7646 seconds
Number of train/test/val images: 1822/261/0
[Dataset::Dataset] end in 35.4331 seconds
[PersSampler::PersSampler] begin
[PersOctree::PersOctree] begin
[PersOctree::ConstructEdgePool] begin
edge_pool_.size() is value 9702
[PersOctree::ConstructEdgePool] end in 0.0749403 seconds
[PersOctree::PersOctree] end in 371.741 seconds
[PersSampler::PersSampler] end in 377.338 seconds
[Hash3DAnchored::Hash3DAnchored] begin
Warning: FullyFusedMLP is not supported for the selected architecture 70. Falling back to CutlassMLP. For maximum performance, raise the target GPU architecture to 75+.
Warning: FullyFusedMLP is not supported for the selected architecture 70. Falling back to CutlassMLP. For maximum performance, raise the target GPU architecture to 75+.
[Hash3DAnchored::Hash3DAnchored] end in 13.7505 seconds
Warning: FullyFusedMLP is not supported for the selected architecture 70. Falling back to CutlassMLP. For maximum performance, raise the target GPU architecture to 75+.
Warning: FullyFusedMLP is not supported for the selected architecture 70. Falling back to CutlassMLP. For maximum performance, raise the target GPU architecture to 75+.
n_nodes_before is value 3169
n_nodes_compacted is value 3117
tree_nodes_.size() is value 3117
[F Renderer.cpp:206] Check failed: std::isfinite((colors).mean().item())
Aborted (core dumped)

Same problem, have you solved it?

I met the same problem when running on my custom data. I check the code for half day and finally find that It is caused by dataset.factor=2 in config file when no half-resolution images exist.
Specifically, when using dataset.factor=2 (which is specified in wanjinyou.yaml), run.py tries to load images in image_2/ directory, but if no images were found in that directory, images in images/ directory will be loaded instead, which probably be full-resolution images. But intrinsics will still be scaled down by 2 in Dataset.cpp. So the trainer uses mismatched resolution and intrinsic and runs into a crash or fails to converge.
For this, I would recommend raising an error instead of using images/ directory when no images were found in images_2/ directory. @Totoro97
And hope my experience can help you. :-) @sunshineywz123 @qipenggu

I met the same problem when running on my custom data. I check the code for half day and finally find that It is caused by dataset.factor=2 in config file when no half-resolution images exist.
Specifically, when using dataset.factor=2 (which is specified in wanjinyou.yaml), run.py tries to load images in image_2/ directory, but if no images were found in that directory, images in images/ directory will be loaded instead, which probably be full-resolution images. But intrinsics will still be scaled down by 2 in Dataset.cpp. So the trainer uses mismatched resolution and intrinsic and runs into a crash or fails to converge.
For this, I would recommend raising an error instead of using images/ directory when no images were found in images_2/ directory. @Totoro97
And hope my experience can help you. :-) @sunshineywz123 @qipenggu

but for me,there is some images in  image_2

In the situation I met, generating half-resolution images in images_2 directory or appending command line argument dataset.factor=1 to run.py would fix the problem.
-------- 原始邮件 --------
发件人： sunshineywz123 @.>
日期： 2023年5月4日周四 傍晚5:39
收件人： Totoro97/f2-nerf @.>
抄送： dengnianchen @.>, Comment @.>
主 题： Re: [Totoro97/f2-nerf] [F Renderer.cpp:206] Check failed: std::isfinite((colors).mean().item()) (Issue #20)
I met the same problem when running on my custom data. I check the code for half day and finally find that It is caused by dataset.factor=2 in config file when no half-resolution images exist.
Specifically, when using dataset.factor=2 (which is specified in wanjinyou.yaml), run.py tries to load images in image_2/ directory, but if no images were found in that directory, images in images/ directory will be loaded instead, which probably be full-resolution images. But intrinsics will still be scaled down by 2 in Dataset.cpp. So the trainer uses mismatched resolution and intrinsic and runs into a crash or fails to converge.
For this, I would recommend raising an error instead of using images/ directory when no images were found in images_2/ directory. @Totoro97https://github.com/Totoro97
And hope my experience can help you. :-) @sunshineywz123https://github.com/sunshineywz123 @qipengguhttps://github.com/qipenggu
for this reason,what should i do to fix this error?
―
Reply to this email directly, view it on GitHubhttps://github.com/Totoro97/f2-nerf/issues/20#issuecomment-1534414413, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABMDDRPN7TPSCRSRFY3PL4LXEN2NHANCNFSM6AAAAAAXRRAH44.
You are receiving this because you commented.Message ID: @.***>

@sunshineywz123  Hi, I am still trying to figure out what happened here. Could you provide your dataset for my testing, if you don't mind?
@dengnianchen Thank you so much for pointing out that! I should be able to fix it when I have time. I am now rushing to another deadline therefore the response maybe slow.

the code for undistort might has some bugs

the code for undistort might have some bugs, when those code are commented out, the bugs disappear

the code for undistort might have some bugs, when those code are commented out, the bugs disappear

caused by dataset  factor 2,factor=1, no bugs

I met the same problem when running on my custom data. I check the code for half day and finally find that It is caused by dataset.factor=2 in config file when no half-resolution images exist.
Specifically, when using dataset.factor=2 (which is specified in wanjinyou.yaml), run.py tries to load images in image_2/ directory, but if no images were found in that directory, images in images/ directory will be loaded instead, which probably be full-resolution images. But intrinsics will still be scaled down by 2 in Dataset.cpp. So the trainer uses mismatched resolution and intrinsic and runs into a crash or fails to converge.
For this, I would recommend raising an error instead of using images/ directory when no images were found in images_2/ directory. @Totoro97
And hope my experience can help you. :-) @sunshineywz123 @qipenggu

thanks, it solves the bug

I met the same problem when running on my custom data. I check the code for half day and finally find that It is caused by dataset.factor=2 in config file when no half-resolution images exist.
Specifically, when using dataset.factor=2 (which is specified in wanjinyou.yaml), run.py tries to load images in image_2/ directory, but if no images were found in that directory, images in images/ directory will be loaded instead, which probably be full-resolution images. But intrinsics will still be scaled down by 2 in Dataset.cpp. So the trainer uses mismatched resolution and intrinsic and runs into a crash or fails to converge.
For this, I would recommend raising an error instead of using images/ directory when no images were found in images_2/ directory. @Totoro97
And hope my experience can help you. :-) @sunshineywz123 @qipenggu

thank you, it solved the error~

In the situation I met, generating half-resolution images in images_2 directory or appending command line argument dataset.factor=1 to run.py would fix the problem.
…
-------- 原始邮件 -------- 发件人： sunshineywz123 @.> 日期： 2023年5月4日周四 傍晚5:39 收件人： Totoro97/f2-nerf @.> 抄送： dengnianchen @.>, Comment @.> 主 题： Re: [Totoro97/f2-nerf] [F Renderer.cpp:206] Check failed: std::isfinite((colors).mean().item()) (Issue #20) I met the same problem when running on my custom data. I check the code for half day and finally find that It is caused by dataset.factor=2 in config file when no half-resolution images exist. Specifically, when using dataset.factor=2 (which is specified in wanjinyou.yaml), run.py tries to load images in image_2/ directory, but if no images were found in that directory, images in images/ directory will be loaded instead, which probably be full-resolution images. But intrinsics will still be scaled down by 2 in Dataset.cpp. So the trainer uses mismatched resolution and intrinsic and runs into a crash or fails to converge. For this, I would recommend raising an error instead of using images/ directory when no images were found in images_2/ directory. @Totoro97https://github.com/Totoro97 And hope my experience can help you. :-) @sunshineywz123https://github.com/sunshineywz123 @qipengguhttps://github.com/qipenggu for this reason,what should i do to fix this error? ― Reply to this email directly, view it on GitHub<#20 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABMDDRPN7TPSCRSRFY3PL4LXEN2NHANCNFSM6AAAAAAXRRAH44. You are receiving this because you commented.Message ID: @.***>

thank you, it solved the error~


text:
images: display commons image if image="File:*"

some "image" tags in OSM have only "File:*.jpg" as value. This is the filename on Wikimedia Commons!
display them too.

fixed with 7c2bea2bf98b67bb9d8e0c5348a99ea82db22e60

source: gharchive/issue

repo: TransforMap/transfor-map

license: unlicense

license_type: permissive

license_source: bigquery


text:
Fixed possible test failure on date/time rollover

Closes #6

Changes Unknown when pulling 7ff8644a1bff3e64b34cd41987b966b4f0336d26 on feature/fixDateDependancyOnTests into ** on develop**.

source: gharchive/pull-request

authors: brettminnie coveralls

license: mit


text:
Nov 2019

Description of Changes:

How This Was Tested:

Related Issue(s) or Specifications:

Checklist:

[ ] Code follows code style of this project
[ ] Tests added to cover changes
[ ] All new and existing tests passing

Questions / Additional Notes:

@shrubin2 - please fill out the PR description so I know what your trying to do, how you tested it, and any links to designs! That'll help me review this.
Additionally, CI is failing :grimacing:

license: MIT

license_source: github-api


text:
SOPORTE-->Bandeja de tareas: permiso al user Admin para acceder y supervisar a todas las solicitudes

Ambiente Prodcción - v2.5.1
Descripción
El cliente pide acceso para manipular la trazabilidad de las solicitudes de servicios que se realicen desde cualquier rol y así supervisarlas
https://user-images.githubusercontent.com/88331456/224429512-64a4034a-4d1f-49f7-ac87-24bc736844fc.mp4

Solucionado

repo: Trazalog/traz-prod-assetplanner


text:
French docs is missing Labs section

Describe the bug
The English docs site has a "Labs" section here.
This section is missing from the French docs.
@AminGtt , any interest in making a PR?
Reproduction
https://docs.tresjs.org/fr/guide/
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

@andretchen0 I think there was a PR that solved some of this issues https://github.com/Tresjs/tres/pull/645

Hey @alvarosabu ,
As of 7b88bf9, the French is different from the others. It has a repeated text/link to the playground, instead of having the text/link to the lab.

repo: Tresjs/tres


text:
This fixes the factory for ManyToManyField to make Column.multi_choic…

…e_queryset work properly
TODO: tests
Depends on another PR in tri.query to make it work with queries

[Current coverage][cc-pull] is 95.98% (diff: 57.14%)

Merging [#6][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.34%

@@             master         #6   diff @@
==========================================
  Files             3          3
  Lines           545        548     +3
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            525        526     +1
- Misses           20         22     +2
  Partials          0          0

Powered by Codecov. Last update [49c4075...b3a7438][cc-compare]
[cc-base-branch]: https://codecov.io/gh/TriOptima/tri.table/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/TriOptima/tri.table/compare/49c40755f6bf996baf529c99574f6f2301cd86cc...b3a74389b830dc54ab98ca973a63eb49c7b27a32?src=pr
[cc-pull]: https://codecov.io/gh/TriOptima/tri.table/pull/6?src=pr

This has been solved in another commit.

authors: boxed codecov-io


text:
want to add route and controller for setting shareable link in Product

@Trisha-tech , can i create the route and controller for the shareable link. This enhancement will empower users to efficiently manage and share product links, enhancing the accessibility and visibility of products.

@Trisha-tech , can i create the route and controller for the shareable link. This enhancement will empower users to efficiently manage and share product links, enhancing the accessibility and visibility of products.

Hello @Naman197 , Go for it
All the Best

repo: Trisha-tech/OnlineBookSales


text:
Update Kowl to Redpanda Console

https://docs.redpanda.com/docs/platform/quickstart/console-installation/

Have implemented it as a non-breaking change, leaving the old kowl support as is.

repo: TrivadisPF/platys-modern-data-platform


text:
🛑 T:Riza Docs is down

In 2fbc243, T:Riza Docs (https://docs.triza.dev) was down:

HTTP code: 0
Response time: 0 ms

Resolved: T:Riza Docs is back up in 1004372.

repo: TrizaCorporation/Status


text:
Nvidea overlay

Expected behavior
Working Nvidea overlay
Actuall behavior
Not working in windowed mode at all.
Lagging and freezing in fullscreen (windowed mode)
Technical information
PC specs
OS: Win 10 x64
GPU: GTX 960
CPU: i7
Vulkan
Vulkan/SDK version: 1.1.82.0

Behavior has changed in windowed fullscreen mode:
working but lagging while ALT key is pressed + pixelated (maybe no MSAA?!).

repo: Troblecodings/TGEngine


text:
Support function to manipulate middlewares

Fixes https://github.com/TrueCar/gluestick/issues/412

:+1: this looks good! We can merge as soon as we get the updated CLA :)

Ping :)

authors: grabbou toddw

repo: TrueCar/gluestick-shared


text:
Bug: Boundless Injury

when i use inflict spells they don't get the boundless healing's bonus of being boundless regard to it's bonuses.
like a level 20 caster casts a cure light wounds, it normall should heal 1d8+5 as is max 5, but with boundless healing they heal 1d8+20
inflict doesnt do that though. inflict still deals 1d8+5 damage

Fixed

authors: RevanStarforge Truinto

repo: Truinto/DarkCodex


text:
Split headers break mobile usability (according to Google crawler)

Issue Summary
The new split layout header cards work great on actual phones, but cause Google to report (in Google Search Console) that the page is not mobile responsive because it is too wide.  The problem originates in this CSS:
.kg-layout-split .kg-header-card-text {
    padding: 12vmax 4vmax;
}

And in the 'quirky' behavior of the Google mobile crawler, which rather than scrolling, just sets the page height as tall as it needs to be.  So if you have a fairly long page (5000px), that causes the horizontal padding to be 100px on each side.  Which causes the page to be wider than the viewport (but only for the Google mobile crawler, because there are no phones that tall).  Which causes Google to report that it won't serve the fancy new landing page as a search result for mobile phone searches.  Argh!
Steps to Reproduce
See above.
Occurs in unmodified Casper, and Ruby, and probably all themes, because it's coming from the cards css, not the theme css.
Ghost Version
5.59
Node.js Version
not relevant, happens on my 16.x and Ghost Pro
How did you install Ghost?
Both self host in VPS and on Ghost Pro.
Database type
MySQL 8
Browser & OS version
Google crawler problem.
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

Hey there, thank you so much for the detailed bug report.
That does look like something that shouldn't happen! A PR to fix this issue would be very welcome 🙂

Hi  @daniellockyer , @cathysarisky
The issue with Google reporting that the page is not mobile responsive due to excessive width can be resolved by modifying the CSS  -
.kg-layout-split .kg-header-card-text {
    padding: 12vmax 4vmax;
    max-width: 100%;
    box-sizing: border-box;
}

max-width: 100%; -  This addition ensures that the header cards won't extend beyond the width of the viewport, addressing the issue where Google reports excessive width.
box-sizing: border-box; - This property ensures that padding is included within the defined width of the element, preventing padding from adding to the overall width.
Please let me know if could I fix this issue. I need guidance to set up Ghost locally on my machine.

Hey @iprasandeep , I believe this issue (which was bigger than just that one spot I saw it in) has been addressed recently in this commit:
https://github.com/TryGhost/Ghost/commit/c759f419a1868676b8e57fcffc36b4d1cb3b8732
If you need help settings up Ghost locally, please post over on forum.ghost.org.

authors: cathysarisky daniellockyer iprasandeep

repo: TryGhost/Ghost


text:
Recommendations do not work for Instagram profiles

Issue Summary
The recommendations-related /check endpoint does not correctly parse the response from Instagram:

Prepopulated fields are generic, not from the profile
The recommendation feature_image is base64 encoded and causes the recommendation to be rejected upon attempting to save.

Steps to Reproduce
Add a recommendation to an Instagram Profile.
Observe prepopulated fields.
Attempt to save it.
Details (from this forum post: https://forum.ghost.org/t/valid-url-issue-with-recommendations/45281/8 )
Prior to saving, what's populating the preview looks like a login page, not the profile page entered, although the URL is the profile page.  And the image URL is actually base64-encoded, which is probably what's breaking things on attempting to save.
Ghost Version
Ghost Pro
Node.js Version
Ghost Pro
How did you install Ghost?
Ghost Pro
Database type
MySQL 8
Browser & OS version
Chrome, Windows 10, freshly updated
Relevant log / error output
Here's what the /check endpoint returns:

{
    "recommendations": [
        {
            "id": null,
            "title": "Login • Instagram",
            "description": null,
            "excerpt": "Welcome back to Instagram. Sign in to check out what your friends, family & interests have been capturing & sharing around the world.",
            "featured_image": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAKAAAADTbI/v/KBhsCbrDBhoAbbAi4wQYbAm6wIeAGG2wIuMGGgBtssCHgBhsCbrDB/wlKajuIhIz6AQAAAABJRU5ErkJggg==",  (Truncated before posting issue)
            "favicon": "https://static.cdninstagram.com/rsrc.php/v3/yG/r/De-Dwpd5CHc.png",
            "url": "https://www.instagram.com/yomikestevens/",
            "one_click_subscribe": false,
            "created_at": null,
            "updated_at": null
        }
    ]
}
===================================

And here's the 422 response on trying to save the recommendation with the (incorrect) check response above.

{
    "errors": [
        {
            "message": "Validation error, cannot save recommendation.",
            "context": "recommendations.0.featured_image must be a valid URL",
            "type": "ValidationError",
            "details": null,
            "property": null,
            "help": null,
            "code": null,
            "id": "f6d58dd1-d573-11ee-9d12-7d870f824854",
            "ghostErrorCode": null
        }
    ]
}

Code of Conduct

[X] I agree to be friendly and polite to people in this repository

Hi @cathysarisky , Can you assign me this task?


text:
Ghost 1.0 development installation

About the Ghost 1.0 (currently alpha) development installation instructions at:
Working with Ghost - How to install & develop with Ghost 1.0 (Wiki)
https://github.com/TryGhost/Ghost/wiki/Working-with-Ghost
they are already useful, but could be improved and completed, as detailed below.
Currently they are, in summary:
git clone git@github.com:TryGhost/Ghost.git ghost
cd ghost
npm run init
grunt dev

Later it's also mentioned:
knex-migrator init

etc.
Some details to improve:

It should be mentioned that the Yarn dependency manager must be installed before running npm run init.
A workaround for a current Yarn bug would be useful to mention. That bug can give: error We don't have permissions to touch the file "/usr/bin/ember". What worked for me was to run: export PATH="$PATH:$HOME/.config/yarn/global/node_modules/.bin" after installing Yarn. This path addition works at least for Linux and Mac.
It would be useful to mention that knex-migrator init should be run during the installation, to init the database before starting Ghost with grunt dev.
A better and more common Git workflow is mentioned at Git workflow · TryGhost/Ghost Wiki, and I think it should be also used in the Ghost 1.0 dev install instructions: "Each developer should fork the core Ghost repo into a repo of their own and clone this as their local repo. Remember to add the main repo as a remote" That is, cloning locally our fork on GitHub (for pull requests, etc.) as remote origin, and setting the official Ghost repo as remote upstream.

After these changes, the Ghost 1.0 dev install works well.

About #3, I've just seen that in other Ghost 1.0-alpha dev install instructions on the README.md, knex-migrator init appears already correctly before grunt dev, as in my opinion should be also on the Wiki. The other details are similar, they could also be completed.

Thanks for the suggestions, we are moving all development and self-hosting docs to docs.ghost.org rather than using the wiki as this has become rather confusing. This is still in progress so let us know if you notice anything else missing :)

authors: cobbspur juan-g


text:
Added backfill migration for members created events

closes https://github.com/TryGhost/Team/issues/1836

Uses the timestamps from the members table to determine the timestamps for the events
Clears the table when downgrading to prevent having multiple rows for the same member

@daniellockyer I think this is ready for final review

authors: SimonBackx allouis


text:
Update Travis dist from Precise to Xenial

The Linux distribution (Precise) defined in .travis.yml is being decomissioned from Travis CI. The following alert can be found when triggering a job:

This job is running on our Precise environment, which is in the process of being decommissioned. Please update to a newer Ubuntu version by specifying dist: xenial in your .travis.yml.

More about this:
https://docs.travis-ci.com/user/reference/overview/#deprecated-virtualization-environments

For the time being, we will remain on trusty as much as possible as it produces builds with a lower version requirement for GLIBC.

This should be no longer relevant 🙂

authors: daniellockyer kewde siikasmaa


text:
開催通知のインデントがおかしい

スマホのみで再現

なおった

repo: Tsuuko/cbbot-py


text:
bboxes1.size(-1) == bboxes2.size(-1)

Hi, i got this error.
Traceback (most recent call last):
File "/home/chen_haoye/WS_SST/SST/tools/train.py", line 234, in
main()
File "/home/chen_haoye/WS_SST/SST/tools/train.py", line 231, in main
meta=meta)
File "/home/chen_haoye/WS_SST/SST/mmdet3d/apis/train.py", line 34, in train_model
meta=meta)
File "/home/chen_haoye/anaconda3/envs/SST/lib/python3.7/site-packages/mmdet/apis/train.py", line 170, in train_detector
runner.run(data_loaders, cfg.workflow)
File "/home/chen_haoye/anaconda3/envs/SST/lib/python3.7/site-packages/mmcv/runner/epoch_based_runner.py", line 127, in run
epoch_runner(data_loaders[i], **kwargs)
File "/home/chen_haoye/anaconda3/envs/SST/lib/python3.7/site-packages/mmcv/runner/epoch_based_runner.py", line 50, in train
self.run_iter(data_batch, train_mode=True, **kwargs)
File "/home/chen_haoye/anaconda3/envs/SST/lib/python3.7/site-packages/mmcv/runner/epoch_based_runner.py", line 30, in run_iter
**kwargs)
File "/home/chen_haoye/anaconda3/envs/SST/lib/python3.7/site-packages/mmcv/parallel/data_parallel.py", line 75, in train_step
return self.module.train_step(*inputs[0], **kwargs[0])
File "/home/chen_haoye/anaconda3/envs/SST/lib/python3.7/site-packages/mmdet/models/detectors/base.py", line 237, in train_step
losses = self(**data)
File "/home/chen_haoye/anaconda3/envs/SST/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
return forward_call(*input, **kwargs)
File "/home/chen_haoye/anaconda3/envs/SST/lib/python3.7/site-packages/mmcv/runner/fp16_utils.py", line 128, in new_func
output = old_func(*new_args, **new_kwargs)
File "/home/chen_haoye/WS_SST/SST/mmdet3d/models/detectors/base.py", line 58, in forward
return self.forward_train(**kwargs)
File "/home/chen_haoye/WS_SST/SST/mmdet3d/models/detectors/voxelnet.py", line 94, in forward_train
*loss_inputs, gt_bboxes_ignore=gt_bboxes_ignore)
File "/home/chen_haoye/anaconda3/envs/SST/lib/python3.7/site-packages/mmcv/runner/fp16_utils.py", line 214, in new_func
output = old_func(*new_args, **new_kwargs)
File "/home/chen_haoye/WS_SST/SST/mmdet3d/models/dense_heads/anchor3d_head.py", line 354, in loss
sampling=self.sampling)
File "/home/chen_haoye/WS_SST/SST/mmdet3d/models/dense_heads/train_mixins.py", line 80, in anchor_target_3d
sampling=sampling)
File "/home/chen_haoye/anaconda3/envs/SST/lib/python3.7/site-packages/mmdet/core/utils/misc.py", line 29, in multi_apply
return tuple(map(list, zip(*map_results)))
File "/home/chen_haoye/WS_SST/SST/mmdet3d/models/dense_heads/train_mixins.py", line 148, in anchor_target_3d_single
gt_labels, input_meta, num_classes, sampling)
File "/home/chen_haoye/WS_SST/SST/mmdet3d/models/dense_heads/train_mixins.py", line 274, in anchor_target_single_assigner
gt_bboxes_ignore, gt_labels)
File "/home/chen_haoye/anaconda3/envs/SST/lib/python3.7/site-packages/mmdet/core/bbox/assigners/max_iou_assigner.py", line 105, in assign
overlaps = self.iou_calculator(gt_bboxes, bboxes)
File "/home/chen_haoye/WS_SST/SST/mmdet3d/core/bbox/iou_calculators/iou3d_calculator.py", line 46, in call
self.coordinate)
File "/home/chen_haoye/WS_SST/SST/mmdet3d/core/bbox/iou_calculators/iou3d_calculator.py", line 125, in bbox_overlaps_nearest_3d
assert bboxes1.size(-1) == bboxes2.size(-1) >= 7
AssertionError

I believe this error is not related to SST. I can not help you If you do not share your analysis and debugging information.

Hi, the bboxes1 takes value from gt_bboxes_3d in nuscenes dataset which is [N,9], bboxes2 I guess is the detection box which has [N, 7] shape. That caused the AssertionError.

Hi, I found the reason, the nuscene dataset default uses the velocity info in gt_bboxes_3d.

authors: Abyssaledge chyohoo

repo: TuSimple/SST


text:
I got no mask on demo scripts

hi, I put our data as cityscape format. And train it successfully and get the final.params model.
But when I evaluate it, got the following result:
##################################################
what           :             AP         AP_50%
##################################################
person         :          0.000          0.000
rider          :            nan            nan
car            :            nan            nan
truck          :            nan            nan
bus            :            nan            nan
train          :            nan            nan
motorcycle     :            nan            nan
bicycle        :            nan            nan
average        :          0.000          0.000
And got no mask on demo scripts.
would you please help to suggest the problem happened in train process or some other reanson.
Thank you.

Have you tried our model in cityscapes datasets?

authors: greatgeekgrace huangzehao

repo: TuSimple/mx-maskrcnn


text:
fix(button): not not click when loading

close #1601

感觉 loading 也不影响点击

@07akioni   when I click the button in loading, I will always request events

authors: 07akioni LYErin jahnli

repo: TuSimple/naive-ui


text:
lab_01

Основной код программы
Блок-схемы алгоритмов
Оформление отчета

замерять все красиво в терминальчике

3
Подумать над красивым терминалом (замерять там память и время)

🐴  Введение
Аналитическая часть
🐴 Конструкторская часть
Технологическая часть
Исследовательская часть
Заключение
Список литературы

Основные придирки к отчету:

АА по-середине (на титульнике)
Не "метод", а "реализация алгоритма"
2.4 съехал в оглавлении
Поставить правильный номер формулы
Функция 1.4 описать, что делает
Неправильно стоит номер формулы 1.6
Нумерация должна быт посередине
0 за полями
Списка из двух элементов не бывает
Рисунки сразу после пояснения
Таблица съехала
У таблицы заголовок слева
Русские обозначения
Источники, а литература

✅


text:
Extension to interact with the public Scratch API

Could you add an extension that connects to the scratch api? Because all the other methods are complicated and the turbowarp extensions dont work with it. I would code it myself but I have no idea how.

Do they mean things like getting how many views a project has?

I assume so
For anyone that wants to do this, you may want to either use our trampoline (https://trampoline.turbowarp.org/proxy/projects/104) or ScratchDB

i am currently working on a prototype. I will see if it works

@GarboMuffin, aren't you talking about S-Grab?

@GarboMuffin, aren't you talking about S-Grab?

S-Grab currently doesn't connect to the public Scratch API and doesn't even work for some users.

@GarboMuffin, aren't you talking about S-Grab?

S-Grab currently doesn't connect to the public Scratch API and doesn't even work for some users.

What does it do then?

yeah a few days ago it was not working and now it is?

if scratchdb is not working it should at least try to access the proxy for turbowarp, https://trampoline.turbowarp.org/

@GarboMuffin, aren't you talking about S-Grab?

S-Grab currently doesn't connect to the public Scratch API and doesn't even work for some users.

Can't we just use GET to access data from api.scratch.mit.edu?

Can't we just use GET to access data from api.scratch.mit.edu?

No, because the Scratch API does not let other sites access it. (TurboWarp uses its own API proxy to access it.)

PR #803 uses TurboWarp's trampoline proxy instead of ScratchDB to fetch stuff from the Scratch API.

repo: TurboWarp/extensions


text:
Win32 tests are very slow on AppVeyor

The Win64 tests usually take around 15 min but the Win32 ones take around 35 min. Is it a good idea to remove the Win32 tests to speed up the CI process?

Closed in favour of #823


text:
How to pipe a path of multipart data?

It is not instantly apparent to me. Thanks.

Piping is currently not possible because of the way we use ImageMagic. Your only option is to pipe the image to a file and s3-uploader can be configured to remove the image on disk for you when it is done resizing and uploading.

Great! Thanks for the info!

authors: Starefossen nikkwong


text:
[FEATURE] Hide/Unhide unverified assets

Аbstract
It is really only recommended for user safety that they trade assets which have had some level of due dilligence performed on them first. TurtleNetwork utilizes their IDD services to provide Ticker and Authorizations to assets on the TurtleNetwork: Qualified, Gateway, etc
Motivation and Purposes
This is to give users a curated and non cluttered default experience, but they can very easily through a toggle in the settings, under advanced, show all assets.
Specification
User has to already have enabled the advanced features through the check box in settings. Then they will see under the set script button a toggle for assets: "Show ALL assets" (switchie)

How do the assets get verified?

How do the assets get verified?

By sending a ticker request either to TN core team, or another data service provider.
Only the people who allowed this data provider will see this ticker

Closed for now

repo: TurtleNetwork/TurtleNetworkGUI


text:
Add tests for modules and re-structure test files

Description
This PR adds some tests for modules.

Please note WIP.

Ok, I will wait before reviewing it then.

@snowteamer We're ready for a round of review.

authors: Twaha-Rahman snowteamer

repo: Twaha-Rahman/e-commercify


text:
feat(metrics): Add more metrics

For issue #274

Hi @TwiN
Thx for your comments, I've apply some change for your advices.

Hi @TwiN
The request changes in comment have applied.
Plz check thx a lot :)

Codecov Report

Merging #278 (b1d9a0f) into master (08b31ba) will increase coverage by 0.02%.
The diff coverage is 52.38%.

@@            Coverage Diff             @@
##           master     #278      +/-   ##
==========================================
+ Coverage   83.70%   83.72%   +0.02%
==========================================
  Files          53       53
  Lines        3485     3508      +23
==========================================
+ Hits         2917     2937      +20
- Misses        442      446       +4
+ Partials      126      125       -1

Impacted Files
Coverage Δ

core/endpoint.go
72.48% <52.38%> (-1.96%)
:arrow_down:

alerting/provider/googlechat/googlechat.go
94.11% <0.00%> (+0.93%)
:arrow_up:

config/maintenance/maintenance.go
100.00% <0.00%> (+3.79%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 08b31ba...b1d9a0f. Read the comment docs.

hi @TwiN
I added the ut for core.Endpoint.Type()

@wei840222 Awesome work, thank you for the contribution!

authors: TwiN codecov-commenter wei840222

repo: TwiN/gatus


text:
Tweaks and improvements for low-end devices

Hi,
Thanks for working so hard with this bot.
As promissed, I am sending the pull request with the changes I've made so that the bot works seamlessly on my RPi. #17

I added 4 command line arguments
Added a timeout for the blacklisted urls (streams that went down or failed many times)
The config "load_timeout_secs" increases the page.load timeout.
And, there's an option to hide the videos (this also helps to lower the CPU usage, while still keep to bot gaining drops)

Thank you for the contribution! I want to request a few changes before merging this PR.

Instead of manually specifying the timeout for every page.goto() call, use page.setDefaultTimeout() in the constructor of TwitchDropsBot. The page is reused so this only has to be set once.
The rimraf, and typescript dependencies can be devDependencies instead of dependencies. The tsc dependency can be removed since it is already replaced by typescript.

Hi @TychoTheTaco,
I think I've fulfilled all your requests, it's the first time I've tried to mess with Node.js and Typescript. So thanks for your patience!

I made some minor changes to fix a couple things, but everything looks good now so I will merge it.

authors: FelipeCalliari TychoTheTaco

repo: TychoTheTaco/Twitch-Drops-Bot


text:
TypeError: _log() got an unexpected keyword argument 'completion'

I got an error:
Error
TypeError: _log() got an unexpected keyword argument 'completion'

Error: TypeError: _log() got an unexpected keyword argument 'completion'
at handleResponse (http://localhost:1212/renderer.dev.js:240484:48)
at processMessageQueue (http://localhost:1212/renderer.dev.js:240299:17)
at http://localhost:1212/renderer.dev.js:240283:13

I'm using python-lsp-server with Electron and monaco-editor. The code is here https://github.com/pplonski/electron-monaco-python-lsp
I get the error wile write:
import numpy
numpy.random.

Is this issue from monaco-languageclient or from python-lsp-server?
Details how to reproduce the problem: https://github.com/python-lsp/python-lsp-server/issues/119
Thank you!

Based on the error message and the stack trace you provided in https://github.com/python-lsp/python-lsp-server/issues/119, I think it's safe to say that there's something going wrong with the language server itself.

Fixed by downgrading jedi to 0.17.2. Thank you!

authors: pplonski rcjsuen

repo: TypeFox/monaco-languageclient


text:
feat: Implements infinity scroll api

기존과 같은 방식으로 pageNum을 보내주면 됩니다.

ex) http://localhost:8080/api/v2/posts?page=143

기본으로 10개씩 Post를 제공합니다.
이번엔 전체 개수는 제공하지 않아요.
그래서 페이지 번호를 미리 계산할 수 없어요.
이건 무한 스크롤을 위해서 기존과 다르게 이 다음에도 제공할 수 있는지 확인하는 것을 last field로 확인하시면 됩니다.
즉, last = false 이면 계속 요청하시면 되고, last = true이면 마지막 페이지라는 의미입니다.

넵 확인했습니다아

authors: DolphaGo Hyevvy

repo: TypeSpring/Paging


text:
🛑 Migasfree Server OPL is down

In 54e34b7, Migasfree Server OPL (https://migasfree.opl.uab.cat) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Migasfree Server OPL is back up in b13f6cf after 4 minutes.

repo: UAB-OPL/opl-uab-monitoring


text:
🛑 Web OPL is down

In b6e5455, Web OPL (https://opl.uab.cat) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Web OPL is back up in ac04db0 after 5 minutes.


text:
Option for downloading Specific Language only.

Your Feature Request
i think downloading the whole package of language which one don't need is really useless and it would be better if you provide this feature of selecting specific language of one's need and download it.

It is already possible to select only the desired languages and scripts for the installation. What is missing?

There is one

authors: Sayem-Ahmed-Shayeed stweil

repo: UB-Mannheim/tesseract


text:
Peer Feedback

Hey group-2,
Congratulations on completing milestone1! I’m sure Beth would really like your dashboard. Here are a few thoughts from group-1:
What we really liked:

We think you’ve a really novel concept and your pitch is great. The persona fits nicely with your theme and the country-wise trends promote inclusivity.
We really like the color cards for the different brands.
It is also interesting to see the different foundation shades as per best selling brands for different countries.

Some food for thought:

Perhaps you could try using a different color palette for the second chart on the right to keep it distinct from the left chart.
Maybe you can consider expanding the tool-tip of your right chart to also include the mean/median lightness per each brand.
If I were Beth, I would like to know how am I performing in comparison to my competitor brands. The stacked historgams are good but maybe another visualization (violin/boxplot/facet) summarizing comparative performance of brands (where the user has the option to select and compare brands through a widget) might help inform Beth if she should be focusing on selling specific shades, how the brands are performing across countries etc.

All the best!

Hi Group 1:
Thank you for the detailed feedback! Those are great suggestions that would for sure make our app better.
The idea of having a few more widgets for easier comparison was extensively discussed within the group, and is also something we are interested in implementing for future development of the app.
Feel free to come back and explore any future updates. Good luck with your project!
Cheers,
Group 2

Hi Group 1,
Thanks again for the great feedback.
We have decided to use different colours for the two histograms as per your suggestion.
Best,
Ela on Behalf of Group2

authors: elabandari elina-linglin tanmaysharma19


text:
🛑 Student Media - Motley is down

In 037a660, Student Media - Motley (https://motley.ie) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Student Media - Motley is back up in 02e9b64 after 9 minutes.

repo: UCCNetsoc/upptime


text:
Add prominent Browse Collections button above footer on the homepage

This feature is part of Phase 1 of the DAMS v1.5 update (#33).
Add a "Browse All Collections" button above the footer that links to the Browse Collections page (#35)
This button itself will not change size at different viewport sizes, but the padding around it will.

The background is a sliver of feature image with a semi-transparent aggie-blue fill over it. I'll think I'll be making custom image crops for this feature, though we could try filling with the same image used in main feature image and see how it looks.

Skipping v1.5. Not included in v2 design.

repo: UCDavisLibrary/fin-ucd-lib-server


text:
Applying the cookiecutter on an existing repo

Is Your Feature Request Related to a Problem? Please Describe
When @samcunliffe and I had to apply a cookiecutter to an existing repo, we ended up creating the template on a separate directory and copying files across. Is there a better way to do this? And should we document this usecase in this repo?
@matt-graham mentioned that in the ARC festival workshop they tried a different approach to keep the git history.
Describe the Solution You'd Like
Mention this case in the readme and add some steps with the best way to do this.
Describe Alternatives You've Considered
No response
Additional Context
No response

Should it be on the website too? Perhaps a bit out of scope: the website is "just" recommending tools, the root-level README is instructions for how to use the cookie-cutter template.

Do we know if this is a common use-case? Obviously, it would be very handy, but perhaps out of scope? Would be good to document either way, perhaps the website could have a blog section where we write this kind of thing up?

In the workshop we worked on applying the cookiecutter package structure to the existing package in zmek/patientflow. We initially tried following a git merge approach following this guide @paddyroddy pointed me to, with the cookiecutter package created in a new repository to which we added the existing (local) repository as a remote. However we subsequently realised in this case this seemed overkill as there was no history from the new package repository we wanted to preserve so just doing what @sfmig suggested above of copying across the new package structure in to the existing repository in a new commit made sense (we did this in this commit on patientflow).
Some thoughts / comments on doing this for this specific case:

The patientflow package previously had a flat rather than src layout which simplified copying in the new package structure without a risk overwriting any existing top-level __init__.py, with we then just git mving the top-level patientflow directory in to src.
There was an existing .gitignore file in the repository that we decided to retain in favour of the cookiecutter version as it had some customisations as well as the standard Python ignores. I forgot when doing this initially though that I would need to add a rule for the automatically generated _version.py file that setuptools_scm creates.
I also forgot initially to recreate some logic in the previous setup.py file for pulling in package dependencies from a requirements.txt file by setting 'dynamically' in the pyproject.toml.
The ruff configuration we have set up for the cookiecutter template is I would say on the strict side for an existing project, and resulted in a very large wall of errors for patientflow. I recommended to Zella to switch initially to the rules selected in the default configuration  and then maybe add in other rules incrementally later to avoid having to fix so many linting errors at once.

FWIW https://cruft.github.io/cruft/ might be of interest, which I've seen used for exactly this elsewhere (https://github.com/OpenAstronomy/packaging-guide)

Should we just point to Laura's guide?

I have no opinions or useful advice other than I've seen cruft being used before 😄

authors: dstansby matt-graham paddyroddy samcunliffe sfmig

repo: UCL-ARC/python-tooling


text:
Include exemplar data in distribution zip

For #43, although does not address the question of whether the directory should be removed with make clean.
Have checked locally that this adds the files in the zip with no other apparent differences.

Is that better dealt with in a separate PR? I noticed there's another CSV file produced from running the notebooks that is not cleaned (I guess a more recent addition) so perhaps better tackled together. But I can make the change for the data/ directory here too.

Is that better dealt with in a separate PR? I noticed there's another CSV file produced from running the notebooks that is not cleaned (I guess a more recent addition) so perhaps better tackled together. But I can make the change for the data/ directory here too if preferable.

Yeah I think we can probably do that in a separate PR and make sure we're removing all the generated artefacts / not removing anything else we don't want to! Happy for this to be merged.

authors: ageorgou matt-graham

repo: UCL-RITS/doctoral-programming-intro


text:
Add Individual-based modelling course to website

Fixes #1281
@andrew-phillips-1  - I've taken the google doc of the course and put in to .RST format in this PR>.
Some quick questions about this.....

Please check the acknowledgment is correct.
Do you want to add a suggested citation?
Should we remove what we have currently under item 0 on this page (i.e., your slides and video)  --- or should we put them at the top of the new page for this course? (Not sure of the relationship between the tutorial and the full course)

Please check the acknowledgment is correct.
I suggest you change to "This content was created by George Phillips, Loveleen Bansi-Matharu and Andrew Phillips"
Do you want to add a suggested citation?
How about "Phillips G, Bansi-Matharu, Phillips AN.  Building and Understanding Individual Based Models to Inform Health Policy.  https://github.com/UCL/TLOmodel/blob/hallett/add-ibm-course/docs/ibm_course.rst
Should we remove what we have currently under item 0 on this page (i.e., your slides and video) --- or should we put them at the top of the new page for this course? (Not sure of the relationship between the tutorial and the full course)
They are somewhat independent, so I suggest having them as two separate learning resources.
Thanks !

This content was created by George Phillips, Loveleen Bansi-Matharu and Andrew Phillips

Thanks. I've added this. I didn't have a URL for George, so have left it as plain text.

Thanks @andrew-phillips-1  -- I think this is ready to go then.

repo: UCL/TLOmodel


text:
Code Comments Guideline

Draft guidelines for commenting code

Proposed acceptable commenting formats below. These are based on a rant from Linus earlier this year which I tend to agree with
Type A:
/* This is a comment */
Type B:
/*
* This is also a comment, but it can now be cleanly
* split over multiple lines
*/

Type C:
// This can be a single line. Or many. Your choice.
Type D:
/* This is an alternate multi-line format
that isn't horrible, but not kernel style */

(no)
/* Lorem ipsum dolor sit amet

consectetur adipiscing elit
*/

(no-no-no)
/* This is also very nasty

and visually unbalanced */

@a6wu @c3bryant I think this would be a great thing if you used an ESLint file and then anyone working on the repository would also know to follow the same rules (their linter would yell at them if they used the wrong styles).  For reference, I really like the AirB&B javascript style guide (https://github.com/airbnb/javascript) and there is an ESLint ruleset you can use that would be great for ensuring contributors conform as well.

Thanks @srkirkland for PR 61, we will use that going forward

repo: UCSD/now-mobile


text:
[Suggestion] Add metadata specifier to UPROPERTY/UCLASS/USTRUCT etc.

Hello, would it be possible to add metadata specifiers to dumped properties/classes/structs ? (I'm talking about the meta stuff like meta(ClampMin=..., ClampMax=...), you can find a sample on FColor.), also maybe add Category property specifier (if available, this might be exposed only to editor builds idk)
You have a sample of how to get metadata in "UField::GetMetaData" in Engine/Source/Runtime/CoreUObject/Private/UObject/Class.cpp

Unfortunately the MetaData related functions and variables only exist in the UE editor, so the only way to do this would be to glean which specifiers are appropriate from the context of the property at runtime which can be difficult and inaccurate.
I appreciate letting us know where to look though, it's very helpful.

Unfortunately the MetaData related functions and variables only exist in the UE editor, so the only way to do this would be to glean which specifiers are appropriate from the context of the property at runtime which can be difficult and inaccurate. I appreciate letting us know where to look though, it's very helpful.

You're right, didn't saw that was marked EDITORONLY. There might be a way tho as I know some of metadata are used at runtime in production build.

Unfortunately the MetaData related functions and variables only exist in the UE editor, so the only way to do this would be to glean which specifiers are appropriate from the context of the property at runtime which can be difficult and inaccurate. I appreciate letting us know where to look though, it's very helpful.

After talking with a former epic employee here is what he told me about accessing metadata in shipping builds

Not without engine changes.  Some metadata makes it into property flags but most doesn’t
Package level metadata can be promoted to asset registry tags without modifying the engine though

The specific metadata specifier I was interested to was AssetBundles btw. I think we could still get it apart from metadata since they are used at runtime for shipping builds. I'll look at it tmr.

It says it's NULL in the game.


text:
CkIO file read support

Original issue: https://charm.cs.illinois.edu/redmine/issues/1521

CkIO currently only supports writing files.
Branch rohan/ckioread: https://charm.cs.illinois.edu/gerrit/gitweb?p=charm.git;a=shortlog;h=refs/heads/rohan/ckioread

Original date: 2017-04-21 02:41:13

Semi-related stackoverflow question: http://stackoverflow.com/questions/43272225/file-handling-support-in-charm

Add documentation for readthedocs describing how to use the new CkIO features.

repo: UIUC-PPL/charm


text:
AMPI implements subcommunicators in an unscalable fashion

Original issue: https://charm.cs.illinois.edu/redmine/issues/1963

This is the real issue behind the following: https://charm.cs.illinois.edu/redmine/issues/1962
MPI_COMM_SELF is the pathological case of creating 'n' 1-element chare arrays, but in general AMPI currently implements subcommunicators using chare arrays, which has a scaling limit in terms of the number of collections Charm++ supports in its 64-bit ID. After the patch for the above issue, AMPI can run with up to 16M ranks. If we want to go further we will run out of collection bits in the ID.

Original date: 2018-08-09 19:44:49

An alternative would be to use sections to implement subcommunicators, with additional data structures to keep track of ranks in subcommunicators from the parent communicator.
Two things we want in AMPI's implementation of subcommunicators:

Same syntax for AMPI to communicate over all communicators (using the same type of proxy for remote method invocation, same syntax for bcasts, and same syntax for reductions, etc).
Consistent performance whether messaging over all communicators.

MPI_COMM_SELF currently also several KB per VP, which could be saved if we lazily/dynamically create MPI_COMM_SELF on demand, when needed.
Also, a nice feature of sections is that collective messages don't need to go to all PEs if the elements don't span all PEs (as they do for chare arrays).


text:
Make array broadcasts node aware

Very little change was required to get this working at a basic level, because array bcasts are based on group broadcasts. Main changes were adding array broadcast message types (one for the initial broadcast, and one for forwarding the broadcast to each group on a node), stopping CkArray from modifying the message, and adding a nokeep broadcast to CkArray.

The change is now fixed and ready for everything but ZC and BigSim. I will need to work with Nitin to figure out what is going wrong with ZC, and BigSim is now being deprecated.

The change is now fixed and ready for everything but ZC and BigSim. I will need to work with Nitin to figure out what is going wrong with ZC, and BigSim is now being deprecated.

I've pushed the fixes to the ZC implementation based on the changed semantics for chare array broadcast. These fixes include the following changes:

Not resetting the message type to ForBocMsg (which was required previously in order to reuse the same message)
For broadcast from non-zero root, by default recvBroadcast was called. This has been modified to called the expedited and noKeep versions of recvBroadcast based on entry method options.

Updated to master that removes BigSim. @epmikida is this ready for review?

Updated to master that removes BigSim. @epmikida is this ready for review?

Yes.

There is a crash in MPI-smp during automated testing in examples/charm++/zerocopy/entry_method_post_api/prereg, which is a p2p message test. It seems spurious, so I'll restart this build.
make[5]: Entering directory '/home/travis/build/UIUC-PPL/charm/mpi-linux-x86_64-smp/examples/charm++/zerocopy/entry_method_post_api/prereg'
make -C simpleZeroCopy test OPTS='-optimize -production  -g -Werror=vla' TESTOPTS='+setcpuaffinity'
make[6]: Entering directory '/home/travis/build/UIUC-PPL/charm/mpi-linux-x86_64-smp/examples/charm++/zerocopy/entry_method_post_api/prereg/simpleZeroCopy'
../../../../../../bin/testrun  +p4 ./simpleZeroCopy 32 +balancer RotateLB +setcpuaffinity
Running on 4 processors:  ./simpleZeroCopy 32 +balancer RotateLB +setcpuaffinity
charmrun>  /usr/bin/setarch x86_64 -R  mpirun -np 4  ./simpleZeroCopy 32 +balancer RotateLB +setcpuaffinity
Charm++> Running on MPI version: 3.1
Charm++> level of thread support used: MPI_THREAD_FUNNELED (desired: MPI_THREAD_FUNNELED)
Charm++> Running in SMP mode: 4 processes, 1 worker threads (PEs) + 1 comm threads per process, 4 PEs total
Charm++> The comm. thread both sends and receives messages
Converse/Charm++ Commit ID: 0fa61e4
CharmLB> Load balancer assumes all CPUs are same.
Charm++> cpu affinity enabled.
Charm++> Running on 1 hosts (1 sockets x 1 cores x 2 PUs = 2-way SMP)
Charm++> cpu topology info is gathered in 0.078 seconds.
Charm++> Warning: the number of SMP threads (8) is greater than the number of physical cores (2), so threads will sleep while idling. Use +CmiSpinOnIdle or +CmiSleepOnIdle to control this directly.
WARNING: Multiple PEs assigned to same core, recommend adjusting processor affinity or passing +CmiSleepOnIdle to reduce interference.
CharmLB> RotateLB created.
send: completed
Fatal error in MPI_Irecv: Invalid buffer pointer, error stack:
MPI_Irecv(153): MPI_Irecv(buf=(nil), count=840, MPI_BYTE, src=0, tag=1378, comm=0x84000002, request=0x7ffff003b910) failed
MPI_Irecv(118): Null buffer pointer

I see some potential race conditions with the ZC changes which may need to be addressed.

I've modified that code to not write into the envelope and just use the GroupID instead.

I see some potential race conditions with the ZC changes which may need to be addressed.

I've modified that code to not write into the envelope and just use the GroupID instead.

Ah I didn't realize those calls were only on one PE. But I agree, I think the consistency of not modifying the message is a good change to make anyways.

authors: epmikida evan-charmworks nitbhat


text:
MSPSDS-639: Format full details tab of case to follow designs

Mostly cosmetic changes, plenty of stuff expected to be displayed in the 'Report' part is not really implemented yet.

Pull Request Test Coverage Report for Build 962

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.892%

Totals

Change from base Build 959:
0.0%

Covered Lines:
1564

Relevant Lines:
1702

💛  - Coveralls

repo: UKGovernmentBEIS/beis-mspsds


text:
[LCS-334] - Update Urls & relevant associated field names

current-property-address to tenant-current-address
landlord-agent to landlord-or-agent

The ticket says to change the urls, but you've changed all of the field names as well? Is there a reason for that?

@lennym maybe my eyes are deceiving me but where have I tried the field names?
I did change the address key which will affect the field names in the hof-behaviour-address-lookup but I thought I should change that because 1. I thought it needs to match with the url to get it to work as part of the config.  2. Keep it consistent.

Your eyes are deceiving you then. Most of the changes to acceptance tests are changes to the names/ids of the fields being filled in.
If you haven't changed the field names then these changes shouldn't have been made, as you're now instructing the tests to fill out fields that don't exist.

Ok I get what you're saying. I've now updated the PR name to match what you're referring to.  Looking at my PR, I think I've updated the feature files in accordance with the changes I've made to the addresses
Would you suggest not changing the fields in the future?  I just find it confusing if the address key is different to the step.  I would think it's clearer and helpful when you are searching

You need to bear in mind that changing field names can have serious side-effects that result in bugs.
Specifically, the customer email is still expecting a field named current-property-address that will need to be updated before this can be merged.

Good point @lennym
Would you like me to change it back in that case?

You've come this far... so might as well press on. Just need to update the email code.

OK, I've learnt my lesson, in the future, I'll avoid changing field names when changing the URLs especially if the service is at a mature state with complex code such as the email service

The addresses mentioned in the customer emails will also need to be updated:

https://github.com/UKHomeOffice/right-to-rent-check/blob/master/apps/right-to-rent-check/behaviours/customer-email.js#L17
https://github.com/UKHomeOffice/right-to-rent-check/blob/master/apps/right-to-rent-check/translations/src/en/email.json#L11-L13

Nice one @lennym I've updated now

Will merge once changes from #97 are in.

authors: lennym sulthan-ahmed

repo: UKHomeOffice/right-to-rent-check


text:
Integrate state

Added simple JSON api to handle company data and implement redux with react to manage state and allow a new company to be added.

The build is a little big still, but after analysing the output it looks like a big chunk of that size is momentjs and jquery, so after this branch I can switch to another time formatter that is way smaller or just write one.
All the fields work except the radio button.
Also this cancels out the other pull request a form value are controlled by redux form

repo: UKTradeInvestment/data-hub-prototype


text:
Kotlin

This pull request migrates the code from Java to Kotlin 1.4 in a new branch called kotlin just made to avoid conflicts with other classmates who are working with Java's main branch

Sorry for the inconvenience. Make the PR against to the newly created kotlin branch. The PR interface does not allow to create new branchs on demand.


text:
Remove x joined channel message

The bot's message when someone joins a new channel is a bit distracting from the broader conversation. Something we could do is either make it a dm response only or unique to the #bot-testing channel.

Closing as we're getting rid of our managed channel system for Discord's version

authors: JamesDearlove campbell-mcfadden

repo: UQComputingSociety/uqcsbot-discord


text:
Feature: Single Select Prototype API for Hourly Apportioned Emissions Data in JSON

Feature Benefit
(What is this feature's benefit hypothesis? Proposed measurable benefit to the end-user or business)
Scope
As a user, I want to access data through a UI, so that I may filter and sort the data based off different criteria.
As a user, I want to access data through an API, so that I may receive my data without going through a UI.
This prototype API serves two parts:

Support #172 prototype UI by providing data for the UI
Provide data to the end-user through a publicly accessible API

Display only 5 years of data (2015-2019)
Display data for all US states - including Alaska, Hawaii, Puerto Rico, District of Columbia
Filter Criteria

Date (custom date range, no hour range)
State
Facility (Filter by facility name AND/OR by ORIS code)
Unit type
Unit fuel type
Control technologies
Operating hours only (if selected, return only operating hours. If not selected, return all data), OP Time greater than 0

Filtering will use "AND" condition - find results that match all criteria, not any criteria
Filter criteria will be in a multi select for all options (not in scope for 2.3)
Sorting by any criteria is out of scope for 2.3
Data Elements
The prototype will include Hourly emissions (no aggregation at unit level)
Include all data elements currently in FTP hourly emissions data EXCEPT for FAC_ID and UNIT_ID
Results will be displayed in a preview in table format
Each data element will be a column
Table limited to 50 results in preview (Showing 50 of XXXX records)
Will provide option to download data results
Query results will include:
STATE | FACILITY_NAME | ORISPL_CODE | UNITID | OP_DATE | OP_HOUR | OP_TIME | GLOAD (MW) | SLOAD (1000lb/hr) | SO2_MASS (lbs) | SO2_MASS_MEASURE_FLG | SO2_RATE (lbs/mmBtu) | SO2_RATE_MEASURE_FLG | NOX_RATE (lbs/mmBtu) | NOX_RATE_MEASURE_FLG | NOX_MASS (lbs) | NOX_MASS_MEASURE_FLG | CO2_MASS (tons) | CO2_MASS_MEASURE_FLG | CO2_RATE (tons/mmBtu) | CO2_RATE_MEASURE_FLG | HEAT_INPUT (mmBtu) | PRIMARY_FUEL_INFO | SECONDARY_FUEL_INFO | UNIT_TYPE_INFO | SO2_CONTROL_INFO | PART_CONTROL_INFO | NOX_CONTROL_INFO | HG_CONTROL_INFO

Design API, contracts, entities - Meet to design the API (identify contracts, entities, and end points) - size:5
#529
Set up service repo - tasks: scaffold, set up controller services, and repo classes - size: 2
#527
Convert schemas - tech team - see migrate MP data - size: 3 - Jason
#532
Extract and load data in database (cloud.gov) -  tech team - size: 5 - Jason
#531
Build contracts, entities Size: 3
#528
Build repo, develop query logic - size: 5
#533

Next steps:

Validate date range
Validate state
Validate unit type
Validate unit fuel type
Validate control technologies
Validate facility
Validate ORIS code

Split this feature to be only for the single select API option. Will create a new feature for the multiple select option (including validation updates) and will move the new feature to PI 3.

Split this feature to be only for the single select API option. Will create a new feature for the multiple select option (including validation updates) and will move the new feature to PI 3.

See feature #639

See feature #639

authors: JorjaComer davidkwartler

repo: US-EPA-CAMD/easey-ui


text:
Gridmet: Run gridmet tools with drb PRMS reaches shp

translate gridded dataset to the specified vector aoi (polygons or polylines) using grid2shp_xagg package.

Extract gridmet data
re-grid to the defined aoi boundary
Export as Netcdf

This will be conducted for the following gridmet variables:

Max and min temperature
precipitation accumulation
downward surface shortwave radiation
wind-velocity
humidity (maximum and minimum relative humidity and specific humidity)

Repo: https://github.com/USGS-R/drb_gridmet_tools

For the temperature forecasting project, we need the capability of matching grids to polylines and points as well. The REAME of the linked repo says grid to hru polygon, but could this be expanded to HRU polygons, segment polylines, and points of interest ?

Interpolated PRMS

Are the PRMS HRUs being interpolated somehow? Or is this supposed to be a climate dataset (gridMET?) instead of PRMS?

For the temperature forecasting project, we need the capability of matching grids to polylines and points as well. The REAME of the linked repo says grid to hru polygon, but could this be expanded to HRU polygons, segment polylines, and points of interest

@jzwart Thanks for specifying this. Yes, I will update the readme.
@jds485 I am definitely misusing the term 😄 . I'll update, and do let me know if it doesn't describes the process as it should.

UPDATE:
Gridmet pulled and processed for our catchments here repo drb_gridmet_tools
Processing time to get all our variables of interest is ~1:30 min 😨 , for me today. (has run faster previously, so might be need to test in new env.)
Code branch branch:Gridmet_processing_v1 to be merged to main after cleaning repo. Issue #2 to resolve
Questions:

Do we want to integrate gridmet_split_script.py into R targets pipeline and use reticulate? Will take a long time to build
Should we load the gridmet output directly from  1_fetch/in/. Note that the output is too large to be stored in our github repo?

I think it's okay to keep the gridmet processing separate from our pipeline. We can save the gridmet data to S3 and read that into our pipeline as a target (similar to the ScienceBase targets)

Alright, I'll share with you via teams the sample of the file so we can determine how to fetch, munge, process.

UPDATE:
gridmet_split_script.py merged to main in repo drb_gridmet_tools
Issue #3 to resolve.
Passed to @jsadler2 for further processing of data for drb-inland-salinity-ml that can then be added to pipeline.

authors: jds485 jzwart msleckman

repo: USGS-R/drb-inland-salinity-ml


text:
rigorously compare french data & outputs to bob's versions

predictions for P,R,K should be very very similar
identify known differences, e.g. in the exact coefficients for the garcia-gordon model, etc.
bob's final, french-specific code is in 'stream_metab_usa/starter_files/One station metab code.R'

see test-french.R (PR pending)

repo: USGS-R/streamMetabolizer


text:
unit tests using python driver and pytest

This PR includes unit tests for the sources in vic_run and drivers/shared.  The unit tests use the pytest infrastructure and require the python driver from #221.
Python requirements:

pytest
numpy
netCDF4 (optional but encouraged)
VIC/drivers/python
tonic (optional but required if using the run_tests.py utility.

To do:

[x] Fix problems with tests / functions that use double pointers.
[x] Include tests for testable functions in vic_run (not all functions will be possible)
[ ] Update .travis.yml to build Python driver and run unit tests
[ ] drivers/shared functions that don't have test or have broken tests that are likely due to errors in the test itself:

[ ] calc_root_fraction
[ ] compress_files
[ ] compute_treeline
[ ] free_vegcon (double pointer issue)
[ ] initialize_snow (double pointer issue)
[ ] initialize_soil (double pointer issue)
[ ] initialize_veg (double pointer issue)
[ ] come back to make_dmy
[ ] soil_moisture_from_water_table

There are some tests that are currently failing.  My guess is that most of these are errors in the tests, but it has already been a nice tool for finding a few smaller bugs.  Those fixes will come in separate pull requests.

Can you put the VIC changes in a separate pull request from the python files? For example, change the print format in strftime or whitespace in C files isn't really part of this PR

yes.  can do.

@bartnijssen - this is ready for a review.  I'd like to merge these tests into develop ASAP and continue to build on them as we go.  There are a lot of functions that don't have test written for them yet and we will add them as necessary.  For example, my next task is to test the new calendar functions and I'll fill that test set in as I go.
There are some commented out tests that will require more work on the driver side but I'm leaving them in the code with TODO comments.
The current dependency stack for the tests is:

python 3.4
numpy
scipy
netCDF4

In a separate PR, I will add support for python 2.7 and add the travis build for these tests.

I'll merge the PR so you can move forward, but more documentation about what you are testing (does not need to be long) will be needed. I am not convinced that we are testing edge cases in many cases.

Thanks.  As you said, if we want to get to the place where we are testing edge cases, we have a long way to go.  Hopefully, what I've done here is provided enough unit test examples that we can write new tests as we go along.

authors: bartnijssen jhamman

repo: UW-Hydro/VIC


text:
Simplify channel title

Remove estimated because on most discord clients it cuts off the "in-upl" part. We can explain the estimation in the channel with the bot

Introduction:
This update addresses the previous implementation's issue of truncated channel names in most Discord clients, resulting in a loss of information. By removing the "estimated" portion of the channel name and providing a more concise representation, we ensure that the channel name remains informative and visible to users.
Problem:
The original code utilized the word "estimated" in the channel name to represent an approximation of the number of people in an "upload" state. However, the inclusion of "estimated" led to the truncation of the "in-upl" part of the channel name in most Discord clients. As a result, users were unable to see the complete information.
Solution:
To resolve this issue, we have removed the "estimated" portion of the channel name and updated the code to provide a more concise representation of the number of people in an "upload" state. This change ensures that the channel name remains informative and fully visible in most Discord clients. The code now follows this structure:
Explanation:
The updated code checks if there is only one person in an "upload" state and appends "person-in-upl" to the channel name, e.g., "1-person-in-upl". If there are multiple people in an "upload" state, it appends "people-in-upl" instead, e.g., "{people_count}-people-in-upl". The new channel name structure ensures that the information is clear and not truncated in most Discord clients.
Regarding the estimation explanation, it is now assumed that this information will be provided in the channel where the bot is active, rather than in the channel name itself. This approach maintains the necessary context without negatively impacting the channel name's visibility.
Conclusion:
The updated code provides a more efficient and user-friendly solution for representing the number of people in an "upload" state within a Discord channel's name. By removing the "estimated" portion and utilizing a more concise representation, we ensure that users can view the complete channel name in most Discord clients. The estimation explanation will now be provided within the channel where the bot is active, maintaining the necessary context without impacting visibility.

lgtm

Excellent commit and write up, but be a little more verbose next time please.

authors: Nicell mdberkey wallenben

repo: UW-UPL/people-counter-discord-bot


text:
Meeting Agendas

Basic Information
The project manager will upload the meeting agenda here every week before the meeting to help other members prepare for it
Other Information
Update the file name with the current week

Meeting 3_ Week 3
Meeting3_Agenda_WEEK3.docx

Meeting 4_ Week 3 Agenda
Meeting4_Agenda_WEEK3.docx

Meeting 5_Week 4 Agenda
Meeting5_Agenda_WEEK4.docx

Meeting 6_Week 5 Agenda
Meeting6_Agenda_WEEK5.docx

Meeting 7a_Week 6 Agenda
Meeting7a_Agenda_WEEK6.docx

Meeting8_Agenda_WEEK7.docx

Meeting9_Agenda_WEEK8.docx

Meeting10_Agenda_Week9.docx

Meeting_Agenda_Week10.pdf

Meeting_Agenda_Week11.pdf

Project finished!

authors: Alexkszzz TheOneHoff lmbhov


text:
Add some diagnostics

Hello! I'm one of the authors of Firebase Crash Reporting. I'm trying to figure out why you're having trouble uploading crashes. Can you accept this change, re-run, and then update https://github.com/UglyBlueCat/quickstart-ios/blob/master/crashreporting/upload_sym_error with the output of that?
I was prohibited from updating to High Sierra for a while on my work computer and wasn't able to repro on Sierra. Now that I've finally been allowed to upgrade to High Sierra, I tried again and still couldn't repro.
I also just want to say that I appreciate your efforts to give as much information as possible!
Lastly, I'm also interested in the output of the following two commands:
which curl
curl --version
Thanks!

Hi Mike,
Do you still need this?
I'm sorry, but my work has become very busy as I approach a deadline.
Robin
Robin Spinks
07710 520048
uglybluecat@googlemail.com
On 18 January 2018 at 00:29, Michael Haney notifications@github.com wrote:

Hi Robin,
Odd request: can you please build and run 3 times and upload (or email me)
the output of the 3rd run? I really appreciate your help, and I think I'm
getting to the bottom of the issue.
On Tue, Jan 16, 2018 at 7:29 PM Michael Haney mikehaney24@gmail.com
wrote:

Thanks for uploading the new log.
You're right--Crashlytics is the way to go, but we definitely don't want
to there to be any issues for our existing customers of Firebase Crash,
so
I'm trying to fix this.
To that end, I've been trying to reproduce this issue and haven't been
able to. I'll keep trying and ask for more information if I need any.
Thanks a lot for your help so far!
On Tue, Jan 9, 2018 at 3:46 AM Robin Spinks notifications@github.com
wrote:

Hi Micheal,
I've saved the log into
https://github.com/UglyBlueCat/quickstart-ios/
blob/master/crashreporting/Build%20CrashReportingExample_
2018-01-09T11-00-59.rtf
I don't know why I didn't see that save button before, but now you have
the
whole part of the log relevant to the issue.
here's the output of the two commands you requested:
$ which curl
/usr/bin/curl
$ curl --version
curl 7.54.0 (x86_64-apple-darwin17.0) libcurl/7.54.0 LibreSSL/2.0.20
zlib/1.2.11 nghttp2/1.24.0
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps
pop3
pop3s rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB
SSL
libz HTTP2 UnixSockets HTTPS-proxy
I should have told you that we have now installed crashlytics, as per
your
colleagues suggestion, and it is working fine, so we have removed
firebase
crash reporting.
We figured google probably wouldn't pursue this issue as a priority,
since
they appear to be phasing out firebase crash reporting.
You may close this issue if you wish, but I will continue to help you
resolve it if that is your wish, since there may be others with the
issue
who can't (or won't) switch to crashlytics.
Thanks,
Robin
Robin Spinks
07710 520048
uglybluecat@googlemail.com
On 9 January 2018 at 00:29, Michael Haney notifications@github.com
wrote:

Hello! I'm one of the authors of Firebase Crash Reporting. I'm trying
to
figure out why you're having trouble uploading crashes. Can you accept
this
change, re-run, and then update https://github.com/
UglyBlueCat/quickstart-ios/blob/master/crashreporting/
upload_sym_error
with the output of that?
I was prohibited from updating to High Sierra for a while on my work
computer and wasn't able to repro on Sierra. Now that I've finally
been
allowed to upgrade to High Sierra, I tried again and still couldn't
repro.
I also just want to say that I appreciate your efforts to give as much
information as possible!
Lastly, I'm also interested in the output of the following two
commands:
which curl
curl --version
Thanks!
You can view, comment on, or merge this pull request online at:
https://github.com/UglyBlueCat/quickstart-ios/pull/1
Commit Summary

Add some diagnostics

File Changes

M crashreporting/Firebase/Crash/upload-sym-util.bash
https://github.com/UglyBlueCat/quickstart-ios/pull/1/files#diff-0
(2)

Patch Links:

https://github.com/UglyBlueCat/quickstart-ios/pull/1.patch
https://github.com/UglyBlueCat/quickstart-ios/pull/1.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/UglyBlueCat/quickstart-ios/pull/1, or mute the
thread
<
https://github.com/notifications/unsubscribe-auth/
AC4FNOfig4UFjIFDT9mOWzlVfx_K-mwyks5tIrLXgaJpZM4RXJia
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/UglyBlueCat/quickstart-ios/
pull/1#issuecomment-356261857>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABCFgjHUqu_
1w4KSGNAJ2aNMTUg_-dCqks5tI1F7gaJpZM4RXJia>
.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/UglyBlueCat/quickstart-ios/pull/1#issuecomment-358496458,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC4FNGTl3V9obVinkngattqZw22a9fqBks5tLpBjgaJpZM4RXJia
.

If you're able to do it, we'd appreciate it and I'd try to use that
information to solve the problem. For now, after spending 5 full days
trying to reproduce this, I've moved on to other issues.
On Mon, Feb 12, 2018 at 2:57 AM Robin Spinks notifications@github.com
wrote:

Hi Mike,
Do you still need this?
I'm sorry, but my work has become very busy as I approach a deadline.
Robin
Robin Spinks
07710 520048
uglybluecat@googlemail.com
On 18 January 2018 at 00:29, Michael Haney notifications@github.com
wrote:

Hi Robin,
Odd request: can you please build and run 3 times and upload (or email
me)
the output of the 3rd run? I really appreciate your help, and I think I'm
getting to the bottom of the issue.
On Tue, Jan 16, 2018 at 7:29 PM Michael Haney mikehaney24@gmail.com
wrote:

Thanks for uploading the new log.
You're right--Crashlytics is the way to go, but we definitely don't
want
to there to be any issues for our existing customers of Firebase Crash,
so
I'm trying to fix this.
To that end, I've been trying to reproduce this issue and haven't been
able to. I'll keep trying and ask for more information if I need any.
Thanks a lot for your help so far!
On Tue, Jan 9, 2018 at 3:46 AM Robin Spinks notifications@github.com
wrote:

Hi Micheal,
I've saved the log into
https://github.com/UglyBlueCat/quickstart-ios/
blob/master/crashreporting/Build%20CrashReportingExample_
2018-01-09T11-00-59.rtf
I don't know why I didn't see that save button before, but now you
have
the
whole part of the log relevant to the issue.
here's the output of the two commands you requested:
$ which curl
/usr/bin/curl
$ curl --version
curl 7.54.0 (x86_64-apple-darwin17.0) libcurl/7.54.0 LibreSSL/2.0.20
zlib/1.2.11 nghttp2/1.24.0
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps
pop3
pop3s rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile GSS-API Kerberos SPNEGO NTLM
NTLM_WB
SSL
libz HTTP2 UnixSockets HTTPS-proxy
I should have told you that we have now installed crashlytics, as per
your
colleagues suggestion, and it is working fine, so we have removed
firebase
crash reporting.
We figured google probably wouldn't pursue this issue as a priority,
since
they appear to be phasing out firebase crash reporting.
You may close this issue if you wish, but I will continue to help you
resolve it if that is your wish, since there may be others with the
issue
who can't (or won't) switch to crashlytics.
Thanks,
Robin
Robin Spinks
07710 520048
uglybluecat@googlemail.com
On 9 January 2018 at 00:29, Michael Haney notifications@github.com
wrote:

Hello! I'm one of the authors of Firebase Crash Reporting. I'm
trying
to
figure out why you're having trouble uploading crashes. Can you
accept
this
change, re-run, and then update https://github.com/
UglyBlueCat/quickstart-ios/blob/master/crashreporting/
upload_sym_error
with the output of that?
I was prohibited from updating to High Sierra for a while on my work
computer and wasn't able to repro on Sierra. Now that I've finally
been
allowed to upgrade to High Sierra, I tried again and still couldn't
repro.
I also just want to say that I appreciate your efforts to give as
much
information as possible!
Lastly, I'm also interested in the output of the following two
commands:
which curl
curl --version
Thanks!
You can view, comment on, or merge this pull request online at:
https://github.com/UglyBlueCat/quickstart-ios/pull/1
Commit Summary

Add some diagnostics

File Changes

M crashreporting/Firebase/Crash/upload-sym-util.bash
https://github.com/UglyBlueCat/quickstart-ios/pull/1/files#diff-0
(2)

Patch Links:

https://github.com/UglyBlueCat/quickstart-ios/pull/1.patch
https://github.com/UglyBlueCat/quickstart-ios/pull/1.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/UglyBlueCat/quickstart-ios/pull/1, or mute the
thread
<
https://github.com/notifications/unsubscribe-auth/
AC4FNOfig4UFjIFDT9mOWzlVfx_K-mwyks5tIrLXgaJpZM4RXJia
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/UglyBlueCat/quickstart-ios/
pull/1#issuecomment-356261857>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABCFgjHUqu_
1w4KSGNAJ2aNMTUg_-dCqks5tI1F7gaJpZM4RXJia>
.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<
https://github.com/UglyBlueCat/quickstart-ios/pull/1#issuecomment-358496458
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AC4FNGTl3V9obVinkngattqZw22a9fqBks5tLpBjgaJpZM4RXJia
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/UglyBlueCat/quickstart-ios/pull/1#issuecomment-364889756,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABCFgto-3465Citq5E7Q7QlYHGqU5tYvks5tUBk2gaJpZM4RXJia
.

Hi Micheal,
I finally got some time to do this for you, but the build was successful
all three times.
Maybe a recent apple update has fixed an issue in macos or xcode.
Robin
Robin Spinks
07710 520048
uglybluecat@googlemail.com
On 12 February 2018 at 18:34, Michael Haney notifications@github.com
wrote:

If you're able to do it, we'd appreciate it and I'd try to use that
information to solve the problem. For now, after spending 5 full days
trying to reproduce this, I've moved on to other issues.
On Mon, Feb 12, 2018 at 2:57 AM Robin Spinks notifications@github.com
wrote:

Hi Mike,
Do you still need this?
I'm sorry, but my work has become very busy as I approach a deadline.
Robin
Robin Spinks
07710 520048
uglybluecat@googlemail.com
On 18 January 2018 at 00:29, Michael Haney notifications@github.com
wrote:

Hi Robin,
Odd request: can you please build and run 3 times and upload (or email
me)
the output of the 3rd run? I really appreciate your help, and I think
I'm
getting to the bottom of the issue.
On Tue, Jan 16, 2018 at 7:29 PM Michael Haney mikehaney24@gmail.com
wrote:

Thanks for uploading the new log.
You're right--Crashlytics is the way to go, but we definitely don't
want
to there to be any issues for our existing customers of Firebase
Crash,
so
I'm trying to fix this.
To that end, I've been trying to reproduce this issue and haven't
been
able to. I'll keep trying and ask for more information if I need any.
Thanks a lot for your help so far!
On Tue, Jan 9, 2018 at 3:46 AM Robin Spinks <
notifications@github.com>
wrote:

Hi Micheal,
I've saved the log into
https://github.com/UglyBlueCat/quickstart-ios/
blob/master/crashreporting/Build%20CrashReportingExample_
2018-01-09T11-00-59.rtf
I don't know why I didn't see that save button before, but now you
have
the
whole part of the log relevant to the issue.
here's the output of the two commands you requested:
$ which curl
/usr/bin/curl
$ curl --version
curl 7.54.0 (x86_64-apple-darwin17.0) libcurl/7.54.0 LibreSSL/2.0.20
zlib/1.2.11 nghttp2/1.24.0
Protocols: dict file ftp ftps gopher http https imap imaps ldap
ldaps
pop3
pop3s rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile GSS-API Kerberos SPNEGO NTLM
NTLM_WB
SSL
libz HTTP2 UnixSockets HTTPS-proxy
I should have told you that we have now installed crashlytics, as
per
your
colleagues suggestion, and it is working fine, so we have removed
firebase
crash reporting.
We figured google probably wouldn't pursue this issue as a priority,
since
they appear to be phasing out firebase crash reporting.
You may close this issue if you wish, but I will continue to help
you
resolve it if that is your wish, since there may be others with the
issue
who can't (or won't) switch to crashlytics.
Thanks,
Robin
Robin Spinks
07710 520048
uglybluecat@googlemail.com
On 9 January 2018 at 00:29, Michael Haney <notifications@github.com

wrote:

Hello! I'm one of the authors of Firebase Crash Reporting. I'm
trying
to
figure out why you're having trouble uploading crashes. Can you
accept
this
change, re-run, and then update https://github.com/
UglyBlueCat/quickstart-ios/blob/master/crashreporting/
upload_sym_error
with the output of that?
I was prohibited from updating to High Sierra for a while on my
work
computer and wasn't able to repro on Sierra. Now that I've finally
been
allowed to upgrade to High Sierra, I tried again and still
couldn't
repro.
I also just want to say that I appreciate your efforts to give as
much
information as possible!
Lastly, I'm also interested in the output of the following two
commands:
which curl
curl --version
Thanks!
You can view, comment on, or merge this pull request online at:
https://github.com/UglyBlueCat/quickstart-ios/pull/1
Commit Summary

Add some diagnostics

File Changes

M crashreporting/Firebase/Crash/upload-sym-util.bash
<https://github.com/UglyBlueCat/quickstart-ios/
pull/1/files#diff-0>
(2)

Patch Links:

https://github.com/UglyBlueCat/quickstart-ios/pull/1.patch
https://github.com/UglyBlueCat/quickstart-ios/pull/1.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/UglyBlueCat/quickstart-ios/pull/1, or mute
the
thread
<
https://github.com/notifications/unsubscribe-auth/
AC4FNOfig4UFjIFDT9mOWzlVfx_K-mwyks5tIrLXgaJpZM4RXJia
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/UglyBlueCat/quickstart-ios/
pull/1#issuecomment-356261857>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABCFgjHUqu_
1w4KSGNAJ2aNMTUg_-dCqks5tI1F7gaJpZM4RXJia>
.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<
https://github.com/UglyBlueCat/quickstart-ios/
pull/1#issuecomment-358496458
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/
AC4FNGTl3V9obVinkngattqZw22a9fqBks5tLpBjgaJpZM4RXJia
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/UglyBlueCat/quickstart-ios/
pull/1#issuecomment-364889756>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABCFgto-
3465Citq5E7Q7QlYHGqU5tYvks5tUBk2gaJpZM4RXJia>
.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/UglyBlueCat/quickstart-ios/pull/1#issuecomment-365018163,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC4FNLx4QxnR54juMUAIAMkNWLJw8ykjks5tUIQngaJpZM4RXJia
.

repo: UglyBlueCat/quickstart-ios


text:
the loss of the finetune

Thanks for your implementation.when I finetune the model using your train.py  with the pre-trained model on my own data ,the loss didn't convergence.Do you have any suggesstion?

Thanks for your implementation.when I finetune the model using your train.py with the pre-trained model on my own data ,the loss didn't convergence.Do you have any suggesstion?

I had the same problem，loss can only converge to about 1.0---1.5, It's no longer going down. is that the case for you？？

This is my experiment's result.
Since I reset my computer, I need to set the environment again to train it again. Please wait for that.
Since the loss is not the average value over the whole epoch and it is the loss of each batch, it may seem like diverging or vibrating. But it is still in training. So I suggest you to check

The actual output image
Measure the MAE / f-measure score by measure_test.py
Plot the loss-epoch graph or use the smooth option in tensorboard. It may show a declining trend.

I have another question，the loss in your code is  0.5 0.5..0.8..1，But here's the author's code

I would like to know why it is not the same as the one set by the author. Looking forward to your reply, thank you very much！

@zicair
In the PiCANet paper Chapter 5.3,
The whole net-
work is trained end-to-end using stochastic gradient descent
(SGD) with momentum. Since deep supervision is adopted
in each decoding module, we empirically weight the losses
in D7
, D5
, D4
, · · · , D1 by 0.5, 0.5, 0.5, 0.8, 0.8, and 1,
respectively, without further tuning.
And I followed the coefficients in the paper

@Ugness  ,I change my learning_rate,this is my best train loss,

but I test it on PASCAL-S ,the max F-score  is 0.82-0.83,I think it maybe poor.

authors: Dailleson RaoHaobo Ugness zicair

repo: Ugness/PiCANet-Implementation


text:
Document how to automerge dependabot PRs

🚀 Feature Request
By default, dependabot spams PRs, causing many notifications/emails. It would be nice to set up auto-merging of at least the patch-level PRs.
📎 Additional context

enable auto-merging in the General settings

create an automerge action (example here). I personally removed the entire second if condition so that all dependabot PRs are automerged.

Thanks, I think the once a week updates are sensible. And I fully agree with you that auto-merging should be up to developer discretion, I just feel like it would be valuable to document how to do it in the repo set-up.

Agree, I will optimize the documentation to tell the developer that there is a possibility of automatic merging.


text:
execution time

Hello,
for this command line
model = '${PATH_TO_PRETRAINED_MODEL}/ChartVLM/base/'  #${PATH_TO_PRETRAINED_MODEL}
which model, we need to provide ?
Also why the execution time is too high for one image ?

Hi, please refer to ../ChartVLM-base or ../ChartVLM-large that contains instruction_adapter, base_decoder and auxiliary_decoder.
As for the execution time, most of the time is used to load the model. And the speed also depends on the device you utilized (we conduct inference task on one single A100).
Thanks for you issues and we will try to optimize overall execution time.


text:
Some tests failing on OSX

Commit 805a488 broke a number of tests on OSX.  See for specifics.

The issue was in libdap2/dapdebug.h.  For some reason, setting DAPDEBUG 1 and OCDEBUG 1 causes a number of failures on OSX.  Fixed in 805a488

repo: Unidata/netcdf-c


text:
Issue while reading data directly from S3

To report a non-security related issue, please provide:

the version of the software with which you are encountering an issue
current master in GitHub

environmental information (i.e. Operating System, compiler info, java version, python version, etc.)
Ubuntu 16.04

a description of the issue with the steps needed to reproduce it
Trying to read a publicly available file from Amazon S3

If you have a general question about the software, please view our Suggested Support Process.
Hi Unidata team,
I am unsure if this is the right place the ask, but it definitely seems the most active. So please forgive me if this is not the correct place.
I am trying to read a public file from S3 through nc_open() but I am getting the following error:
syntax error, unexpected WORD_WORD, expecting SCAN_ATTR or SCAN_DATASET or SCAN_ERROR context: <?xml^ version="1.0" encoding="UTF-8"?><Error>NoSuchKey<Message>The specified key does not exist.</Message><Key>3B-HHR.HDF5.dds</Key><RequestId>C4E7BACB0B8C4258</RequestId><HostId>tROyJy7+a8i/GBuZZQFQXtl95WaKYR4jsK0EBTunVs5Cdr39oswo8nuGYwDBXIkSTHIJ2iJIju0=</HostId></Error>
I came across this  so I assume this is possible, and I am just doing something wrong? Thanks in advanced!

Can you provide a little more info about how you are trying to open the file? What are you passing to nc_open()?   @DennisHeimbigner might be able to provide some insight as well.

Yes, it is possible since we tested it against some similar S3 files.
We will need to know the exact url that you used.

Thanks for the prompt reply!
https://tpch-rmm-fk.s3.eu-central-1.amazonaws.com/3B.nc4
Currently I am using something as simple as this:
(retval = nc_open(argv[1], NC_NOWRITE, &ncid))

You need a marker to tell the library to use byte ranges.
Change the url to this and try again:
"https://tpch-rmm-fk.s3.eu-central-1.amazonaws.com/3B.nc4#mode=bytes"

Thank you very much @DennisHeimbigner ! that worked like a charm.
I still have some questions though:

When should one prefer using nc_http_open vs nc_open api? are they the same or is one subsumed by the other?
If I were to track the total number of requests done to S3, which files should I look into?
Can I make the same assumptions when reading files from S3 as I would when reading files from a local file system? e.g., in terms of data access, are variables accessed only once contiguously if I use nc_get_var_...? I guess at least I will do 1 request for file metadata (is the size of this metadata always the same across nc4 files?) and then 1 request per variable, right?

When should one prefer using nc_http_open vs nc_open api? are they the same or is one subsumed by the other?

The public API for the netcdf library is defined by the union of
the files in include that are of the form netcdf_XXX.h. The
include directory however does contain other, non-public, .h
files; nchttp.h is one such.
Bottom line: since nc_http_open is not public, you should always
use nc_open, which is public.

If I were to track the total number of requests done to S3, which files should I look into?

Not sure I understand the question. Are you asking where to insert code
to track # reads?

Can I make the same assumptions when reading files from S3 as I would when reading files from a local file system? e.g., in terms of data access, are variables accessed only once contiguously if I use nc_get_var_...?

Yes, as far as I know. There is possibly a complication with respect to
chunking. It is possible that when reading what seems to be a contiguous
piece of data, that the HDF5 library will need to read pieces from multiple
chunks and assemble the pieces in memory into one large piece.

I guess at least I will do 1 request for file metadata (is the size of this metadata always the same across nc4 files?)

Metadata size can vary depending on a whole variety of factors, to the number
of reads to read the metadata (for a variable, I assume) might be different
for variables of, for example, different types and rank.

and then 1 request per variable, right?
Yes, except as noted above.

authors: DennisHeimbigner WardF renato2099