-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ARCitect is taking significantly long times to save a file. #320
Comments
Hi @jagdish7396, where is your ARC stored? |
in the downloads folder |
Ok, thanks. I'm asking, since we ran into issues with ARCs stored on network drives, hard drives or cloud folders. |
hello Brilator, is the issue solved? Any solution that you have found or any suggestions you give to streamline the process would be of a great help to me. Thank you so much. |
Can you please create a fresh ARC with only a few studies and check whether you run into the same issue? Thanks |
Is this the same ARC that created the issue #319 ? |
yes it is the same ARC what created issue #319 but then i deleted those files that and recreated them using ARCItect |
Do you run into the same issue when creating a fresh ARC with only a few studies and samples? |
issue #319 was i could not open an ARC itself due to incompatible files(created or modified out side the ARCitect locally oúsing excel) . i corrected that and now the issue is ARCitect is taking too long to save a material sheet created within ARCitect. |
Have you tried this? |
It looks like this is a pretty big ARC and ARCtrl currently has problems with those. Does the save process ever finish? Otherwise you might have ran into another silent error. @HLWeil |
Yes, the save process was finishing. But, it took really a long time. sometimes upto half an hour for the material sheets with more than 3000 observations/plants |
Hey @jagdish7396, I see your ARC contains a lot of assays/studies. Saving all of them might take a while, but usually this is not necessary, as we write only those assay/studies which have been changed. Maybe this somehow did not work. Could you check whether only the assay you made changes to has been overwritten or if ARCitect did overwrite all you assay/study files? |
Actually I have created material sheets for different studies of wheat experiments. So technically I have created new files with lot of data in it. It took a while but actually everything was saved. |
That's good to hear! Just to make sure: If you now make a single change in one of the studies and save, does this now work fast or does it still take a lot of time? |
Maybe access to the preliminary data, that is currently prepared using local storage, could help to reproduce. There is a version uploaded to a nextcloud share: https://ipk-cloud.ipk-gatersleben.de/s/SP6B8G6mkkZeecR Its yet sharable for the community, but could used for bug fixing and test case. |
@jagdish7396 Thanks for the information. Nevertheless, as I'm user like yoiu, please tag the developers instead to get qualified response. |
Hey @jagdish7396, So you openened an ARC, switched to the Assay view and then this error occured? ![]() I would be very interested to see whether the behaviour in your ARC is similar to the one I observed in another ARC that also takes way too long for any action: Especially I'm interested if your console is also being flooded with these |
hii @HLWeil thank you so much for the reply. Here is an attachment you have asked for. |
I see, this is what I expected. Somehow the |
@HLWeil I have also encountered another issue. ARCitect does not run in background. I switched to browser as it was taking too long. When I returned to ARCitect after few minutes it did not open the ARC. But when I stayed on ARCitect it does not take too much time to open the ARC. I repeated 3-4 times to confirm this. Thank you. |
opened a new issue for this #326 |
I have been facing with the ARCitect software. Specifically, when I create a material sheet for a study and attempt to save it, the software takes an excessively long time to process. For small studies, it buffers for over 10 minutes, and for larger studies containing hundreds of observations, the waiting time is significantly longer.
This delay is severely impacting the workflow.
The text was updated successfully, but these errors were encountered: