Seems to be working again now -- maybe it was just a transient failure?

ok

That IP looks like Fastly in Tokyo so it could be a regional outage if you're still having trouble...

(Fastly hosts the CDN in front of Clojars I believe)

I use the VPN from the China

With transforms like this, it's often better to switch one or more structures to a more suitable form first...

...in this case, you want to create an index on :msn for one structure and then use that as a lookup when merging into the other.

(group-by :msn c2) would give you a map from the :msn values in c2 to vectors of matching elements (which you know will only have one entry here).

This seems like https://clojuredocs.org/clojure.set/join

Hmm, yeah, I tend to forget clojure.set has a lot of useful stuff in this area.

I should probably use clojure.set/index more often.

user=> (clojure.pprint/pprint (clojure.set/join (set c1) (set c2)))
#{{:msn "1422",
   :vol 14.559,
   :acc 0.9673,
   :R_e 2039.06,
   :accuracy -3.276,
   :period 0.15}
  {:msn "1433",
   :vol 14.503,
   :acc 0.9636,
   :R_e 2056.02,
   :accuracy -3.639,
   :period 0.16}
  {:msn "1516",
   :vol 14.512,
   :acc 0.9641,
   :R_e 2066.06,
   :accuracy -3.621,
   :period 0.27}
  {:msn "1465",
   :vol 14.592,
   :acc 0.9695,
   :R_e 2043.47,
   :accuracy -3.077,
   :period 0.22}
...

(you lose ordering but you could easily sort-by to get that back)

clojure.set also has a join function

(pretty brute force too)

Whoops, saw group by and index and missed that join was mentioned

Looks like the collections are of equal length in the same order (based on msn). If you can guarantee that is always true, this should work.

(map merge c1 c2)

If you can't guarantee order you could always just sort them both on :msn before calling that on the sorted colls.

https://en.m.wikipedia.org/wiki/Sort-merge_join is really what you want, more optimal on pre-sorted inputs than set/join

Reading that, it sounds to me like a long-winded way of saying to sort the lists on :msn and then step through the sequence, merging each pair together. So, basically do exactly what I just said? :thinking_face:

Well knowing the name makes it easier to search for, and searching this slack turned up all the other times I've linked the article, and some of those have threads with potentially useful example code

> sort the lists on :msn and then step through the sequence, merging each pair together. It sounds like that assumes that every map on each side of the join has exactly one match for the join, which may not be the case (the sort-merge join accounts for this).

https://clojurians.slack.com/archives/C053AK3F9/p1539897330000100?thread_ts=1539897330.000100&cid=C053AK3F9

To me the indexing has to be worth it down the line. It also implies overhead. So N should be large to begin with. If you can do the indexing right at the moment when you construct the data sets it's likely beneficial. Otherwise you could maybe also index the data sets while you merge them: reduce over both collections, put record into index if ID seen for the first time, merge otherwise.

OK, awesome, sorting and combining seems to be the right option.

using futures you could simply use pvalues if you want more control, handling failure, etc there are libraries

I may use promises directly just thought I would see what other have done, what libraries are there I only really found this one https://github.com/metosin/porsas which says experimental, search for databases in the context of clojure promises and async did not return much could be a topic for someone to blog about 🙂

you may be focussing on the keyword "async" too much. In the vast majority of cases, futures are enough and not the bottleneck. You'd usually drown your db before it becomes a problem. And the landscape may vary once java fibers are globally available

still it's interesting from an exploratory point of view

yeah maybe often half the struggle getting the correct search terms 🙂

https://clojuredocs.org/clojure.core/future

yeah going down this path, just figured it was worth checking what the options are in case there are certain considerations which may have been handled in libs or anything like that.

possibly its https://github.com/seancorfield/deps-new#create-an-application

https://github.com/babashka/neil also has some

I've really been enjoying neil for bootstrapping / managing deps.edn projects https://blog.michielborkent.nl/new-clojure-project-quickstart.html

@U7ERLH6JX , will below command to downloads deps ?

clojure -Sdeps 

clojure -P should be better

deps-new and clj-new are two common community projects to create projects from templates clj-new can use a wide variety of existing project templates deps-new provides Clojure CLI specific templates (and has a simpler approach when creating your own templates) https://practical.li/clojure/clojure-cli/projects/create-from-template/

There is not currently any command built into Clojure CLI Tools for generating a new project. It must be done by hand or use a 3rd party tool. The command in your question looks like how you would call to https://github.com/seancorfield/deps-new after it is installed. > will below command to downloads deps ? The -P flag

clojure -P

thanks you all for your inputs, I am going through the tread one by one

@U05254DQM I got below error with the command specified in the doc

clojure -T:project/create :template app :name practicalli/playground
WARNING: Specified aliases are undeclared and are not being used: [:project/create]
No function found on command line or in :exec-fn

To follow that tutorial, you to need to define aliases in your User deps.edn file. For some reason that code is hidden, but you can show it by clicking on “Clojure Aliases for creating projects from templates“ just above the YouTube video.

I've updated the page to hopefully make it cleare that either Practicalli Clojure CLI Config is required or the example aliases Thanks for the feedback

FWIW from my perspective as a teacher it would be really sweet if an absolutely minimal project could be created with the CLI tools alone. Believe it or not, "It must be done by hand or use a 3rd party tool" can be a non-trivial impediment to some newcomers. By minimal I mean just a directory containing a deps.edn that contains {}, and also containing a src folder that contains a single subfolder with the same name as the top-level folder, that in turn contains a single file (might as well be core.clj) that just contains an appropriate minimal ns expression. For some newcomers who don't have experience working at the command line, and may not know the "helpful" things their OS or editor might do with hidden extensions or text encoding, it can be a pretty tedious process to get to the point of working in a minimal project. I have talked with @U0ETXRFEW about adding something that creates such a project within #CBE668G4R, since Calva can work with deps.edn projects without even installing the CLI tools, which is fabulous. But it can't currently create them. Installation of anything can be a pretty big hassle in a class setting, with students using different machines and OSes and having different backgrounds (many of which might include just a single CS course, or less). If I can easily get them over the hump of installing Java and the CLI tools, it would be really great if that gave them all they needed to begin working with code in a project.

> FWIW from my perspective as a teacher it would be really sweet if an absolutely minimal project could be created with the CLI tools alone. - @U06BV1HCH From previous conversations with Alex, this is at least "on the map". There are a lot of open questions about what a project generated by the official CLI tool should look like.

Do you know if any/many of those open questions arise for projects as minimal as what I've suggested? I can imagine lots of questions once you get even slightly more complex, but something like I've suggested at least gets you started (e.g., #CBE668G4R can open and deal with it) without committing one to much of anything.

Keep in mind, though, the fact the Clojure team is interested does not guarantee anything will happen. From the same conversations, Alex also seemed quite positive about the idea of simply relegating such things to tools like Neil. Third party tools bring a benefit of much more flexibility than official tooling could/would. So, honestly, I think the only serious pain point is as it is already is onboarding beginners.

@U064X3EF3 question for you from @U06BV1HCH ^

please please, put any requests or problems on https://ask.clojure.org - I am in way too many threads here and elsewhere that I am seriously overloaded. putting it on ask means that I will (eventually) sweep it into tickets. it also means others can find it via search or similar question prompts, comment on it, and vote on it, which is what we use for prioritization

and yes, I think having means for initial project creation is in scope

So, just in case that ^ wasn't clear @U06BV1HCH, it is definitely being hammocked. If you need more specifics than that, or want to offer feedback or ideas about it, open a question on Ask Clojure.

even if you don't want to do those things, it's still helpful to log it

clojure.set/index

How about some?

(defn some-kv [k v coll] 
  (some (fn [m]
          (when (= v (k m)) m)) 
        coll))

(let [data [{::id 1 ::label "foo"}
            {::id 2 ::label "bar"}]]
  {:a (some-kv ::id 2 data)
   :b (some-kv ::label "foo" data)})
; =>
{:a {:user/id 2
     :user/label "bar" }
 :b {:user/id 1
     :user/label "foo" }}

Why not make two more maps: id->item and label->item? To make such maps, as @U0NCTKEV8 pointed out, clojure.set/index could be useful. But in your case the ids and labels are both unique, so you could do even better. You can follow the "source" link in the API documentation to see how clojure.set/index works.

I would usually define additional lookup maps: (def foo->x (into {} (map (juxt :foo identity) xs))) or (def bar->x (zipmap (map :bar xs) xs))

What about a filter? Or (for with a :when if you have humongous list.